Data converting apparatus, method, and computer product

ABSTRACT

A data converting apparatus includes a storage unit that stores encoded meta-definition information, a data converting function, a conversion rule table, and a conversion rule; an input unit that receives input of data to be converted; a detecting unit that uses the encoded meta-definition information to detect metadata codes for a conversion source and a conversion destination for which the conversion rule code matches; a determining unit that determines whether the detected metadata codes match; a specifying unit that, by referring to a conversion rule and based on the determination result at the determining unit, specifies the data converting function, according to the combination of the metadata codes for the conversion source and for the conversion destination; and a converting unit that uses the specified data converting function to convert the data of the conversion source to have a property prescribed by metadata for the conversion destination.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is based upon and claims the benefit of priority of theprior Japanese Patent Application No. 2009-178446, filed on Jul. 30,2009, the entire contents of which are incorporated herein by reference.

FIELD

The embodiments discussed herein are related to data conversion.

BACKGROUND

A process of integrating extracted data is called physical integration(Extract/Transform/Loading (ETL)). In physical integration, dataextracted from an information source by an extracting function (Extract)is subjected to physical integration (Transformation). Results of theintegration are registered to a user-side by a registering function(Loading). Physical integration is applicable to collective processingexecuted as batch processing. In physical integration, the recency ofinformation is ensured at the extraction of the information. As aresult, overlapping management of the information sources and integratedresults is apt to occur.

One method of achieving physical integration is carried out in such away that functions to be integrated are configured into integrationcomponents as integration logic is written preliminarily in anintegration process logic description language called TransformationDescription Language (TDL) and are registered with a repository. At thetime of execution, the integration components are processed sequentiallyaccording to the TDL integration processing logic (see, e.g., U.S. Pat.Nos. 6,014,670 and 6,339,775).

A process of collecting and integrating, in real-time, data present inmultiple information sources in response to a request from a user-sideis called virtual integration (Enterprise Information Integration(EII)). In virtual integration, necessary information is retrieved andcollected from information sources in response to a request from theuser-side, and the collected data is integrated and returned asintegrated data to the user-side to realize virtual informationintegration. Virtual integration allows the user-side to acquirereal-time information from an information source at the point that theuser-side needs the information, thus enables use of fresh information.Used information is discarded to make overlapping information managementunnecessary.

For information integration such as the physical integration (ETL) andthe virtual integration (EII), a function of converting a format of anoriginal value (From value) into a format of an object value (To value)is essential and is generally referred to as a data type convertingfunction or a cleansing function.

However, the conventional cleansing function is premised onpreliminarily determining a combination of data type and type attributespecifically indicating a property thereof, and a type convertingfunction and a cleansing function for converting the type and theattribute and has a problem in terms of expandability. Specifically, nounit exists for expanding the data type and type attribute possessed bya system in advance, and a combination with the cleansing function and aspecifiable type attribute must be determined in advance, for example,for character code system conversion for a character code systemspecifying a type attribute (char_code) that identifies a character codesystem.

Since no unit exists for ensuring the consistency of type attributes andprocesses in the case of combining and using multiple data types, typeattributes, and cleansing functions, it is problematic that consistencyis impaired at the time of expansion. For example, when a data typesimilar to an existing data type is defined, no unit exits for ensuringconsistency between the existing data type and the cleansing function,which increases the burden on the developer.

If data types, type attributes, type converting functions, and cleansingfunctions are increased, the number of combinations thereof increases,thereby increasing the burden on the developer and problematicallycomplicating management. Since no unit has been provided to efficientlyselect and use necessary cleansing functions for the many combinationsthat exist, performance problematically deteriorates.

SUMMARY

According to an aspect of an embodiment, a data converting apparatusincludes a storage unit that stores encoded meta-definition informationthat assigns a metadata code as a unique code to an element making upmetadata in meta-definition information that defines metadata indicativeof a property related to data of a conversion source and a conversiondestination, a data converting function that converts conversion sourcedata having a property prescribed by the metadata for the conversionsource into conversion destination data having a property prescribed bythe metadata for the conversion destination, a conversion rule tablethat assigns the data converting function according to a combination ofmetadata codes for the conversion source and the conversion destination,and a conversion rule that correlates with each of the conversion ruletables, a relevant metadata code as a conversion rule code; an inputunit that receives input of data to be converted; a detecting unit thatrefers to the encoded meta-definition information stored in the storageunit and detects the metadata codes for the conversion source and theconversion destination for which the conversion rule code matchesbetween the conversion source and the conversion destination; adetermining unit that determines whether the detected metadata codes forthe conversion source and for the conversion destination match; aconverting function specifying unit that, by referring to a conversionrule stored in the storage unit and based on the determination resultobtained by the determining unit, specifies the data converting functionaccording to the combination of the metadata code for the conversionsource and the metadata code for the conversion destination; and aconverting unit that, by using the data converting function specified bythe converting function specifying unit, converts the conversion sourcedata, which is the data to be converted, to have a property prescribedby metadata for the conversion destination.

The object and advantages of the invention will be realized and attainedby means of the elements and combinations particularly pointed out inthe claims.

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory and arenot restrictive of the invention, as claimed.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a diagram of an example of data conversion according to afirst embodiment.

FIG. 2 is a block diagram of a hardware configuration of a dataconverting apparatus according to the first embodiment.

FIG. 3A is a block diagram of a functional configuration of the dataconverting apparatus.

FIG. 3B is a diagram of storage contents of a type converting functionlibrary 302.

FIG. 3C is a diagram of a cleansing function library 303.

FIG. 4 is a diagram of one description example of a cleansingspecification definition file 301.

FIG. 5 is a diagram of an expansion example of the cleansingspecification definition file 301 depicted in FIG. 4.

FIG. 6 is a diagram of a type attribute addition/expansion example ofthe cleansing specification definition file 301.

FIG. 7 is a diagram of a TABLE_A used at a conversion source 101 and aTABLE_B used at a conversion destination 102.

FIG. 8 is a diagram of one description example of a meta-definition file304.

FIG. 9 is a diagram of one description example of the cleansingspecification definition file 301 with inheritance added.

FIG. 10 is a diagram of the inheritance relationship between theSupertype and the Subtype.

FIG. 11 is a diagram of another description example of themeta-definition file 304.

FIG. 12 is a diagram of a cleansing process when the cleansingspecification definition file 301 depicted in FIG. 9 and themeta-definition file 304 depicted in FIG. 11 are used.

FIG. 13 is a diagram of the inheritance relationship when the data type:date type is added as the Subtype.

FIG. 14 is a diagram of an example of the data type conversion throughthe inheritance depicted in FIG. 13.

FIG. 15 is a diagram of an example of the cleansing specificationdefinition file 301 that describes the inheritance relationship betweenthe Supertype (Char type) and the Subtype (date type) depicted in FIG.13.

FIG. 16 is a diagram of one description example of the cleansingspecification definition file 301 with default values defined as typeattributes.

FIG. 17 is an exemplary diagram of the simplification of themeta-definition file 304.

FIGS. 18 to 20 are diagrams of an exemplary cleansing function.

FIG. 21 is a chart of the execution order of the cleansing function.

FIG. 22 is a diagram of an example of the cleansing specificationdefinition file 301 that defines the cleansing function corresponding tomultiple type attributes.

FIG. 23 is a diagram of a cleansing function that executes bothprocesses for the character code system (char_code) and the externalcharacter code system (char_excode) defined in FIG. 22.

FIG. 24 is a diagram of an example of the meta-definition file 304.

FIG. 25 is a diagram of an example of the cleansing specificationdefinition file 301.

FIG. 26 is a diagram of a data type code table 321.

FIGS. 27 to 29 are diagrams of a type attribute code table 322.

FIGS. 30 to 35 are diagrams of a type attribute value code table 323

FIG. 36 is a diagram of a data type conversion rule table 331.

FIGS. 37 to 42 are diagrams of a cleansing rule table 332.

FIG. 43 is a diagram of a conversion rule set 330.

FIG. 44 is a diagram of encoded meta-definition information 340corresponding to FIG. 24.

FIGS. 45 to 49 are diagrams of a first data conversion example using theencoded meta-definition information 340 related to the FULL_NAME inTABLE_A and TABLE_B depicted in FIG. 44.

FIG. 50 is a flowchart of a data converting process procedure of thedata converting apparatus 300 according to the first embodiment.

FIG. 51 is a flowchart of a process procedure (first half) of aninitializing process (step S5001) executed by an initializing unit 311depicted in FIG. 50.

FIG. 52 is a flowchart of a process procedure (second half) of theinitializing process (step S5001).

FIG. 53 is a flowchart of a process procedure of a type attribute valuecode table creating process (step S5104) depicted in FIG. 51.

FIG. 54 is a flowchart of a process procedure of a data convertingprocess (step S5002) depicted in FIG. 50.

FIG. 55 is a diagram of an example of the cleansing specificationdefinition file 301 having a constraint set by a function F1.

FIG. 56 is a diagram of an example of conversion by a function F2.

FIG. 57 is a diagram of an example of conversion by a function F5.

FIG. 58 is a diagram of an example of a function F6.

FIG. 59 is an exemplary diagram of an example of introduction of aconstraint.

FIG. 60 is a diagram of an example of a constraint condition table.

FIG. 61 is a diagram of the conversion rule set 330 when a constraint isadded.

FIGS. 62 to 66 are diagrams of a second data conversion example usingthe encoded meta-definition information 340 related to the FULL_NAME inTABLE_A and TABLE_B depicted in FIG. 44.

FIG. 67 is a flowchart of a data converting process procedure of thedata converting apparatus 300 according to a second embodiment.

FIG. 68 is a flowchart of a process procedure (first half) of aninitializing process (step S6701) executed by the initializing unit 311depicted in FIG. 67.

FIG. 69 is a flowchart of the process procedure (second half) of theinitializing process (step S6701).

FIG. 70 is a flowchart of a process procedure of a control-patternselecting process (step S6802) depicted in FIG. 68.

FIGS. 71 and 72 are flowcharts of a process procedure of a dataconverting process (step S6702) depicted in FIG. 67.

FIG. 73 is a block diagram of a functional configuration of a functionalconfiguration of the data converting apparatus according to theembodiments.

DESCRIPTION OF EMBODIMENTS

Preferred embodiments of the present invention will be explained withreference to the accompanying drawings.

A cleansing function according to the embodiments has a type attributethat specifies a data type and the details thereof as meta-definition ofvalues and gives meta-definition of a conversion source (From side) anda conversion destination (To side) along with data to convert a Fromvalue (conversion source value) into a To value (conversion destinationvalue).

The meta-definition alone is required and the need for conversion logicsand procedures is eliminated. Therefore, expansion is enabled bymanipulating the meta-definition, whereby usability is improved. Sincethe developer is able to manipulate the meta-definition to easily expandand combine functions, developmental burden is reduced. A firstembodiment will hereinafter be described.

FIG. 1 is a diagram of an example of data conversion according to thefirst embodiment. Data conversion according to the embodiment implementsa function that achieves both process efficiency and flexibility with adefinition drive type without the need for logic. Specifically, whendata 104 is converted, if meta-definition 131 of a conversion source 101(From side) is different from meta-definition 132 of a conversiondestination 102 (To side), a converting function 100 is activated forperforming conversion to achieve consistency with the meta-definition132 of the conversion destination.

The meta-definition 103 (131, 132) is information that defines datatypes and type attributes of data at the conversion source 101 and theconversion destination 102. For example, the data types include acharacter string type (Char) and an integer type (Integer). The typeattributes represent more detailed characteristics and include charactercode systems and character types, for example. The character codesystems include, for example, Shift Japanese Industrial Standard (SJIS,Shift JIS), Japanese processing Extended Feature (JEF), and UCS/UnicodeTransformation Format 8 (UTF-8). The character types include a two-bytesize and a one-byte size.

In FIG. 1, as one example, the meta-definition 131 of the conversionsource 101 defines the data type as a character string type, thecharacter code system of the type attribute as Shift JIS, and thecharacter string type as a one-byte size. On the other hand, themeta-definition 132 of the conversion destination 102 defines the datatype as a character string type, the character code system of the typeattribute as UTF-8, and the character string type as a one-byte size.Data 141 of the conversion source 101 is input to the convertingfunction 100 according to the meta-definition 131 of the conversionsource 101. On the other hand, data 142 of the conversion source 102 isinput to the converting function 100 according to the meta-definition132 of the conversion destination 102.

The converting function 100 compares the meta-definition 131 of theconversion source 101 with the meta-definition 132 of the conversiondestination 102 and, if a different portion exists, the convertingfunction 100 converts the differing portion to achieve consistency withthe meta-definition 132 of the conversion destination 102 and outputsthe data. Specifically, the converting function 100 has a data typeconverting function 111 that converts a data type, a character codeconverting function 112 that converts a character code system, and acharacter type converting function 113 that converts a character type.

For example, if the data types are different between the conversionsource 101 and the conversion destination 102, the data type convertingfunction 111 is activated to convert the data type of the data 141 ofthe conversion source 101 into the data type of the conversiondestination 102. Similarly, if the character code systems are differentbetween the conversion source 101 and the conversion destination 102,the character code converting function 112 is activated to converts thecharacter code system of the data 141 of the conversion source 101 intothe character code system of the conversion destination 102. If thecharacter types are different between the conversion source 101 and theconversion destination 102, the character type converting function 113is activated to converts the character type of the data 141 of theconversion source 101 into the character type of the conversiondestination 102.

In the example of FIG. 1, if a character string of “130 YEN” is inputaccording to the meta-definition 131 of the conversion source 101, thecharacter code system and the character type of the type attribute aredifferent between the conversion source 101 and the conversiondestination 102 and therefore, the character code converting function112 and the character type converting function 113 are sequentiallyactivated. Therefore, “130 YEN” of the data 142 output to the conversiondestination 102 is a character string having the character code of UTF-8and the character type of the one-byte size (portion of numericcharacters capable of being converted into one-byte characters).

FIG. 2 is a block diagram of a hardware configuration of a dataconverting apparatus according to the first embodiment (a secondembodiment described hereinafter). As depicted in FIG. 2, the dataconverting apparatus includes a central processing unit (CPU) 201, aread-only memory (ROM) 202, a random access memory (RAM) 203, a magneticdisk drive 204, a magnetic disk 205, an optical disk drive 206, anoptical disk 207, a display 208, an interface (I/F) 209, a keyboard 210,a mouse 211, a scanner 212, and a printer 213, respectively connected bya bus 200.

The CPU 201 governs overall control of the data converting apparatus.The ROM 202 stores therein programs such as a boot program. The RAM 203is used as a work area of the CPU 201. The magnetic disk drive 204,under the control of the CPU 201, controls the reading and writing ofdata with respect to the magnetic disk 205. The magnetic disk 205 storestherein data written under control of the magnetic disk drive 204.

The optical disk drive 206, under the control of the CPU 201, controlsthe reading and writing of data with respect to the optical disk 207.The optical disk 207 stores therein data written under control of theoptical disk drive 206, the data being read by a computer.

The display 208 displays, for example, data such as text, images,functional information, etc., in addition to a cursor, icons, and/ortool boxes. A cathode ray tube (CRT), a thin-film-transistor (TFT)liquid crystal display, a plasma display, etc., may be employed as thedisplay 208.

The I/F 209 is connected to a network 214 such as a local area network(LAN), a wide area network (WAN), and the Internet through acommunication line and is connected to other apparatuses through thenetwork 214. The I/F 209 administers an internal interface with thenetwork 214 and controls the input/output of data from/to externalapparatuses. For example, a modem or a LAN adaptor may be employed asthe I/F 209.

The keyboard 210 includes, for example, keys for inputting letters,numerals, and various instructions and performs the input of data. Atouch-panel-type input pad or numeric keypad, etc. may be adopted. Themouse 211 is used to move the cursor, select a region, or move andchange the size of windows. A track ball or a joy stick may be adoptedprovided each respectively has a function similar to a pointing device.

The scanner 212 optically reads an image and takes in the image datainto the data converting apparatus. The scanner 212 may have an opticalcharacter recognition (OCR) function as well. The printer 213 printsimage data and text data. The printer 213 may be, for example, a laserprinter or an ink jet printer.

FIG. 3A is a block diagram of a functional configuration of the dataconverting apparatus according to the first embodiment (and a secondembodiment described hereinafter). As depicted in FIG. 3A, the dataconverting apparatus 300 includes a cleansing processing unit and aninitializing unit. Specifically, the functions of the cleansingprocessing unit and the initializing unit are implemented by driving theCPU 201 to execute programs stored in a storage device such as the ROM202, the RAM 203, the magnetic disk 205, and the optical disk 207depicted in FIG. 2, for example, or through the I/F 209.

The data converting apparatus 300 uses a cleansing specificationdefinition file 301, a type converting function library 302, a cleansingfunction library 303, and a meta-definition file 304. The cleansingspecification definition file 301, the type converting function library302, the cleansing function library 303, and the meta-definition file304 are stored in a storage device such as the ROM 202, the RAM 203, themagnetic disk 205, and the optical disk 207 depicted in FIG. 2 or areaccessible via the network 214 through the I/F 209.

The cleansing specification definition file 301 defines the propertiesof the data types handled by the data converting apparatus along withthe data type converting function and defines the type attributesdefining detailed properties of the data types along with the cleansingfunction.

The data converting apparatus 300 has an initializing unit 311 and acleansing processing unit 312. The initializing unit 311 reads thecleansing specification definition file 301 and the meta-definition file304 to generate a data type code table 321, a type attribute code table322, and a type attribute value code table 323. The data types, the typeattributes, and the type attribute values are encoded.

The meta-definition file 304 describes the meta-definition 103 depictedin FIG. 1. The initializing unit 311 encodes the meta-definition file304 to generate encoded meta-definition information 340. The encodedmeta-definition information 340 is separately generated for theconversion source 101 and the conversion destination 102.

The initializing unit 311 generates a data type conversion rule table331 from the data type conversion definition of the cleansingspecification definition file 301 and the data type code table 321 andgenerates a cleansing rule table 332 from the cleansing functiondefinition of the cleansing specification definition file 301, the typeattribute code table 322, and the type attribute value code table 323.The initializing unit 311 integrates the data type conversion rule table331 and the cleansing rule table 332 to establish a conversion rule set330. The conversion rule set 330 is binary data, for example. Thus, dataconversion rules are established for conversion from the conversionsource into the conversion destination related to the encoded datatypes, type attributes, and type attribute values.

The cleansing processing unit 312 includes a cleansing control unit 351,a type conversion calling unit 352, and a cleansing calling unit 353.The cleansing control unit 351 reads the From value (original value) 141of the conversion source 101 and the encoded meta-definition information340 on the From side and the To value (object value) 142 of theconversion destination 102 and the encoded meta-definition information340 on the To side and refers to the conversion rule set 330 to controlthe type conversion calling unit 352 and the cleansing calling unit 353.

Specifically, the cleansing control unit 351 compares the encodedmeta-definitions (types) between the From side and the To side todetermine which type converting process is to be executed and drives thetype conversion calling unit 352 to call from the type convertingfunction library 302 and execute the type converting function forexecuting the determined type converting process. Similarly, thecleansing control unit 351 compares the encoded meta-definitions (typeattributes) between the From side and the To side to determine whichcleansing process is to be executed and drives the cleansing callingunit 353 to call from the cleansing function library 303 and execute thecleansing function for executing the determined cleansing process.

FIG. 3B is a diagram of storage contents of the type converting functionlibrary 302. As depicted in FIG. 3B, the type converting functionlibrary 302 stores type converting functions. The type convertingfunctions are specified by a combination of the data type of theconverting source 101 (From side) and the data type of the conversiondestination 102 (To side). The type converting function uses a functionprepared in advance.

FIG. 3C is a diagram of the cleansing function library 303. FIG. 3Cdepicts the cleansing function library 303 of the character code systemconversion. The cleansing function library 303 stores the cleansingfunction when the type attribute is the character code system. Thecleansing function is specified by a combination of the type attributevalue of the From side and the type attribute value of the To side. Thecleansing function also uses a function prepared in advance.

Details of various types of data (the cleansing specification definitionfile 301, the type converting function library 302, the cleansingfunction library 303, and the meta-definition file 304) used in the dataconverting apparatus 300 will be described with examples.

FIG. 4 is a diagram of one description example of the cleansingspecification definition file 301. The cleansing specificationdefinition file 301 depicted in FIG. 4 defines the character string type(Char type) and the integer type (Integer type) as data types. Referencenumeral 401 denotes the definition description of the character stringtype and reference numeral 402 denotes the definition description of theinteger type.

In the definition description 401 of the character string type,reference numeral 411 denotes the description of the type convertingfunction. The description 411 of the type converting function is definedby a DTCV_RULE tag that defines the type conversion. The data type ofthe conversion source 101 (From side) is the character string type andtherefore is not described, and the data type of the conversiondestination 102 is described by an integer type “to=“Integer”” as ato-attribute. A function name called as the type converting function(“character-to-integer conversion” in this example) is assigned as avalue of the DTCV_RULE tag. The function name assigned at this pointacts as a pointer to call the corresponding type converting function.

In the definition description 401 of the character string type,reference numeral 412 denotes a tag that defines a type attribute. Inthe “DATA_ATTR” tag 412 defining a type attribute, a character codesystem (char_code) is described as a type attribute name. A “VALUE” tag413 defining a type attribute value usable as a value of a typeattribute is described as a child tag of the tag 412 defining the typeattribute. Three type attribute values of “SJIS”, “JEF”, and “UTF8” aredefined in this example.

Following the tag 413 defining a type attribute value, a cleansing ruledefinition tag “CL_RULE” 414 is described. In the cleansing ruledefinition tag 414, the type attribute value of the conversion source101 (From side) and the type attribute value of the conversiondestination 102 (To side) are described. For example, if the typeattribute value of the conversion source 101 is Shift JIS and the typeattribute value of the conversion destination 102 is JEF, “from=“SJIS”to =“JEF”” is described in the start tag of the cleansing ruledefinition tag 414. A function name “SJIS_JEF conversion” executing thecleansing function from Shift JIS to JEF (character code systemconversion) is described as a value of the tag. The function nameassigned at this point acts as a pointer to call the correspondingcleansing function.

In the definition description 402 of the integer type, reference numeral421 denotes the description of the type converting function. In thedescription 421 of the type converting function, the data type of theconversion source 101 (From side) is the integer type and therefore isnot described, and the data type of the conversion destination 102 isdescribed by a character string type “to=“Char”” as a value of “to”attribute of the DTCV_RULE tag that defines the type conversion. Afunction name for calling the type converting function(“integer-to-character conversion” in this example) is described as avalue of the DTCV_RULE tag. The function name assigned at this pointacts as a pointer to call the corresponding type converting function.

This cleansing specification definition file 301 is able to define oneor more data types and defines zero or more type attributes and typeattribute values usable as the values of the type attributes for onedata type, as the property of each data type. By using the data types,the type attributes, and the type attribute values usable at theconversion source 101 (From side) and the conversion destination 102 (Toside) defined in this file to describe the property (meta-definition) ofeach value, as the meta-definition file, the meta-definition 131corresponding to the data value 141 of the From side 101 is specifiedand the meta-definition 132 corresponding to the data value 142 of theTo side 102 is specified. As a result, when the meta-definition of theconversion source 101 and the meta-definition of the conversiondestination 102 are delivered to the cleansing processing unit 312depicted in FIG. 3A along with the data of the transform source 101, thecleansing processing unit 312 refers to the conversion rule set 330 toexecute cleansing, such as type conversion and character code systemconversion according to a combination of the types and the typeattributes of the conversion source 101 and the conversion destination102.

By symmetrically defining the conversion source 101 (From side) and theconversion destination 102 (To side) in the cleansing specificationdefinition file 301 (allowing usage in both the From side and To sidedirections), it is not necessary to differentiate the data types, thetype attributes, and the type attribute values usable on the From sideand the To side when the meta-definition file is described. In thevirtual integration (EII), since the data converting function is used inboth the inquiry deconstructing process and the result integratingprocess, and the From side and the To side are reversed in this case, itis essential to symmetrically define the From side and the To side.

FIG. 5 is a diagram of an expansion example of the cleansingspecification definition file 301 depicted in FIG. 4. Although afunction name for calling the type attribute converting function isdescribed for each combination of type attribute values as a cleansingrule in FIG. 4, functions implementing the cleansing function include afunction capable of supporting any combination of type attribute valuesby itself. In FIG. 5, when using a cleansing function capable ofsupporting all the combinations of the relevant type attributes withsingle function, “*” is used as a value of the “from” attribute and the“to” attribute of the cleansing rule definition tag 414. “*” is awildcard representative of all the type attribute values usable in thecorresponding type attributes.

For example, in an underscored line in FIG. 5, the start tag of thecleansing rule definition tag 414 is described as <CL_RULE from=“*”to=“*”>. As a result, if the type attribute of the “char_code” typeattribute of the conversion source 101 is different from the same typeattribute value of the conversion destination 102, the cleansingfunction “CHARACTER CODE SYSTEM CONVERSION” is executed by a functionsandwiched by the start tag and the end tag of the cleansing ruledefinition tag 414.

If described as <CL_RULE from=“A” to=“*”>, when the type attribute valueof the corresponding type attribute of the conversion source 101 is “A”and the same attribute value of the conversion destination 102 is otherthan “A”, the cleansing function is executed by a function sandwiched bythe start tag and the end tag of the cleansing rule definition tag 414.

If described as <CL_RULE from=“*” to=“A”>, when the type attribute valueof the corresponding type attribute of the conversion source 101 isother than “A” and the same attribute value of the conversiondestination 102 is “A”, the cleansing function is executed by a functionsandwiched by the start tag and the end tag of the cleansing ruledefinition tag 414.

FIG. 6 is a diagram of a type attribute addition/expansion example ofthe cleansing specification definition file 301. The cleansingspecification definition file 301 depicted in FIG. 6 is an example ofadding a type attribute of “max_length” that specifies the maximumlength (byte length) of character to the cleansing specificationdefinition file 301 depicted in FIG. 5 after the type attribute:character code system (“char_code”).

By adding the type attribute definition tag <DATA_ATTR>, a typeattribute and a cleansing function able to cope with given data typescan be added. In this example, a length adjusting process for acharacter string can be executed.

The order of the type attribute definitions may be controlled such thata type attribute definition of an important (basic) property is placedearlier to be preferentially executed. In principle, by adding a newtype attribute definition to the tail end, the effect on the existingfunction may be minimized. In this example, “char_code” is a typeattribute that is more important than the type attribute, “max_length”.

The type attribute value may be expanded to make any type attributevalues available by using the type attribute definition <DATA_ATTR> nothaving a <VALUE> tag that defines a type attribute value. For example,by using the type attribute definition not defining a type attributevalue with the <VALUE> tag as depicted within an area demarcated by adashed line in FIG. 6, the type attribute: max_length may take any valueas the type attribute value. This is convenient when it is difficult tolimit a value of the type attribute in advance as in the case ofmax_length that specifies the maximum length (byte length of a characterstring). If the type attribute value is not defined by the <VALUE> tag,since it is difficult to presuppose the value in advance, the cleansingrule definition tag must describe a rule using “*” such as <CL_RULEfrom=“*” to=“*”>. In this case, if the type attribute:max_length isdifferent between the conversion source 101 and the conversiondestination 102, the cleansing function “length ADJUSTMENT” isunconditionally executed.

The meta-definition based on the cleansing specification definition file301 will be described. The cleansing specification definition file 301depicted in FIG. 6 is taken as an example.

FIG. 7 is a diagram of a TABLE_A used at the conversion source 101 and aTABLE_B used at the conversion destination 102. The TABLE_A and theTABLE_B are models of tables defined in the meta-definition file 304.Both the TABLE_A and the TABLE_B define a data type, a type attribute,and a primary key constraint for each column. In the TABLE_A, the datatype of “EMPLOYEE_NUMBER” is the integer type and a primary keyconstraint exists. The data type of “FULL_NAME” is the character stringtype and the character code system of the type attribute is JEF. Themaximum character string length of the type attribute is 20 bytes. Thedata type of “TELEPHONE_NUMBER” is the character string type and thecharacter code system of the type attribute is JEF.

In the TABLE_B, the data type of “EMPLOYEE_NUMBER” is the integer typeand the primary key constraint exists. The data type of “FULL_NAME” isthe character string type and the character code system of the typeattribute is SJIS. The maximum character string length of the typeattribute is 14 bytes. The data type of “TELEPHONE_NUMBER” is theinteger type. The columns of the TABLE_A correspond to the columns ofthe same names in the TABLE_B through (1) to (3).

Although the TABLE_A and the TABLE_B are described as the conversionsource 101 and the conversion destination 102, respectively, thedirection of data conversion generally varies depending on the objectiveof the process. For example, in physical integration (ETL), when thedata model on the information source side and the data model on thetarget side are the TABLE_A and the TABLE_B, respectively, the dataconversion is performed by using columns in the TABLE_A and thecorresponding columns in the TABLE_B as the conversion source 101 andthe conversion destination 102, respectively. In virtual integration(EII), when the physical model on the information source side and thelogic model on the utilization side are the TABLE_A and the TABLE_B,respectively, the data conversion is performed in a process ofconverting a search condition input to the TABLE_B into a searchcondition for the TABLE_A by using a search condition for an objectcolumn of the TABLE_B that is the logic model as the conversion source101 and using a search condition for a corresponding column of theTABLE_A that is the physical model as the conversion destination 102,and the data conversion is performed in a process of converting searchresult data (physical model) on the information source side into data ofthe logic model on the utilization side by using the columns of theTABLE_A as the transition source 101 and using the corresponding columnsof the TABLE_B as the conversion destination. In the followingdescriptions, since the data converting process for converting thephysical model data (TABLE_A) into the logic model data (TABLE_B) in thevirtual integration (EII) is used as an example, it is assumed that theconversion source 101 and the conversion destination 102 are the TABLE_Aand the TABLE_B, respectively.

FIG. 8 is a diagram of one description example of the meta-definitionfile 304. The meta-definition file 304 depicted in FIG. 8 is a file thatdefines the physical model TABLE_A and the logic model TABLE_B and thecorrespondence relationship between the TABLE_A and the TABLE_B.

In this example, the physical model TABLE_A and the logic model TABLE_Bare defined as <R_MODEL> and <V_MODEL>, respectively, and a table nameand a key specification are specified for a name attribute and a keytypeattribute, respectively. The columns making up the tables are defined by<COLUMN> (specifying a column name for the name attribute) and the datatype and the type attribute are defined by <D_TYPE> and <D_ATTR>(specifying a name of the type attribute for the name attribute),respectively, as the properties of the columns. The correspondencerelationship between the columns is defined by <MAP_RULE> to indicatethat the column specified by <FROM_COLUMN> (specifying a table name forthe table attribute) corresponds to <TO_COLUMN> (specifying a table namefor the table attribute). <META_DATA> is a root tag that organizes theentire meta-definition.

If the data of the conversion source 101 (physical model TABLE_A) issubjected to the data conversion and output to the conversiondestination 102 (logic model TABLE_B), since “FULL_NAME” is different inthe type attribute value of the character code system that is the typeattribute, the cleansing from JEF to SJIS is performed. Since the typeattribute regulating the maximum character string length is specified onthe TABLE_B, if the character string length is greater than 14 bytes, acopy is made for 14 bytes and subsequent characters are deleted. Since“TELEPHONE_NUMBER” is different in the data type, type conversion isperformed from the character string type (JEF) to the integer type.

The inheritance of the data type will be described. In the cleansingspecification definition file 301, the cleansing specification may beexpanded by adding description of a data type inheriting an existingdata type. The existing data type is referred to as an Supertype and thenew data type inheriting properties of the Supertype is referred to asan Subtype. This concept is application of the idea similar to thesuccession between classes in object-oriented to the data type. As foreach concept, the data type, Supertype, and Subtype correspond to theclass, Superclass, and Subclass.

The inheritance may be defined by describing “super=“type name ofSupertype”” to specify the Supertype in the definition of the new datatype that is the Subtype. If the inheritance is defined, the data typeof the Subtype inherits all properties such as the type attribute andthe cleansing function possessed by the data type of the Supertype.

An example of addition of the description of the inheritance willhereinafter be described. It is assumed that the data type of theSupertype is the character string type and that the cleansing rule ofthe type attribute: character code system (char_code) is the charactercode system conversion. On the other hand, it is assumed that the datatype of the Subtype is a personal name type and that the cleansing ruleof the type attribute: name_space is a first/second-name spacingprocess.

FIG. 9 is a diagram of one description example of the cleansingspecification definition file 301 with the inheritance added. Thecleansing specification definition file 301 of FIG. 9 is an example ofadding a personal name data type definition description 900 (within anarea demarcated by a dashed line in FIG. 9) to the cleansingspecification definition file 301 depicted in FIG. 4 to enable the usageof the new “personal name type” data and the corresponding cleansingfunction.

In the personal name data type definition description 900,“super=“Char”” is added to the data type: personal name type, asdescription specifying the Supertype. The data type: personal name iscapable of inheriting all the properties such as the type attribute:character code system (char_code) (including the three type attributevalues of SJIS, JEF, and UTF8) and the cleansing function: charactercode system conversion possessed by the character string type specifiedby the description specifying the Subclass.

The Subtype is able to possess name_space (including two type attributevalues of Yes and No) as a unique type attribute independent of theSupertype and the cleansing function: first/second-name spacingfunction. The type attribute: name_space represents the presence ofspace between the first and second names. If the type attribute value isYes, a space is provided, and if No, no space is provided between thefirst and second names.

The type attribute added to the Subtype is added after the typeattribute of the Supertype. Therefore, the type attribute of theSupertype is always handled as a more basic type attribute than the typeattribute of the Subtype.

FIG. 10 is a diagram of the inheritance relationship between theSupertype and the Subtype. FIG. 10 depicts the inheritance relationshipbetween the Supertype and the Subtype in the cleansing specificationdefinition file 301 depicted in FIG. 9. The data type: personal name inthe Subtype inheriting the data type: character string type (Char) ofthe Supertype is able to use the type attribute: character code system(char_code) possessed by the data type: character string type (Char) ofthe Supertype and the type attribute: name_space expanded by the datatype: personal name of the Subtype. The personal name type, i.e., theSubtype inherits all the properties for the character string type(Char), i.e., the Supertype and may be handled as the character stringtype and is additionally defined to be capable of handling “a spacebetween the first and second names”, which is a unique property for thepersonal name type.

FIG. 11 is a diagram of another description example of themeta-definition file 304. In the meta-definition file 304 depicted inFIG. 11, the definition of the “FULL_NAME” column (Char type) isreplaced with the “personal name” type, which is the data type added inFIG. 9, in the TABLE_A and the TABLE_B of the meta-definition file 304depicted in FIG. 8. Therefore, the type attribute “name_space” specificto the personal name type is newly defined; the “FULL_NAME” column ofthe TABLE_A is defined by “name_space=“Yes”” and includes a space; andthe “FULL_NAME” column of the TABLE_B is defined by “name_space=“No””and includes no space. The description of the underline of FIG. 8 (typeattribute: maximum character string length) is deleted in this examplefor the simplicity of description.

FIG. 12 is a diagram of the cleansing process when the cleansingspecification definition file 301 depicted in FIG. 9 and themeta-definition file 304 depicted in FIG. 11 are used. For the“FULL_NAME” column, a personal name “MINENO KAZUO” defined in the datatype: personal name type in the conversion source 101 (From side) issubjected to the cleansing process into the conversion destination 102(To side) in the depicted example. In FIG. 12, the upper side of thedashed-dotted line depicts the cleansing process according to theproperty of the data type: character string type and the lower side ofthe dashed-dotted line depicts the cleansing process according to theproperties specific to the data type: personal name type.

Referring to FIG. 11, for the data type: personal name type in the“FULL_NAME” column of the TABLE_A defined in the conversion source 101,the character code system is JEF and name_space is Yes (includingspace). For the data type: personal name type in the “FULL_NAME” columnof the TABLE_B defined in the corresponding conversion source 102, thecharacter code system is SJIS and name_space is No (not includingspace). Therefore, in FIG. 12, the character code system of the personalname “MINENO KAZUO” is converted from JEF to SJIS by executing thecharacter code system converting function.

On the other hand, name_space of the personal name “MINENO KAZUO” isconverted from Yes (including space) to No (not including space) byexecuting the first/second-name spacing process function. Therefore, inthe conversion destination 102 (To side), the character code system isset to Shift JIS and the space between the second name “MINENO” and thefirst name “KAZUO” is deleted, resulting in the personal name“MINENOKAZUO” (described in Shift JIS).

The data type conversion of the Subtype may inherit properties of theSupertype. Specifically, in the case of a combination with a data typenot requiring a data type conversion unique to the Subtype, the datatype converting process is not defined for the conversion source toinherit the data type converting process of the corresponding data typedefined in the Supertype. If a data type converting process unique tothe Subtype is required, the data type converting process unique to theSubtype is additionally defined to be applied with preference to thedata type converting process defined in the Supertype.

FIG. 13 is a diagram of the inheritance relationship when the data type:date type is added as the Subtype. Focusing attention on the combinationof the data type: character string type (Char) and the data type:integer type (Integer) defined before the addition of the data type:date type in FIG. 13, it is indicated that the mutual data typeconversion is enabled by the data converting processes of“character-to-integer conversion” and “integer-to-character conversion”.On the other hand, focusing attention on the combination of the datatype: date type of the Subtype and the existing data type: integer type,the data type conversion is not explicitly defined between the Subtypeand the data type: integer type. Therefore, the data type conversionwith the integer type defined for the character string type of theSupertype is inherited. Since this means that the data type convertingprocess is executed in the Subtype with the assumption that the data hasthe data type of the Supertype, the operation is performed according tothe concept of the inheritance, which is that “the Subtype inherits theproperties of the Supertype”, and no contradiction occurs.

FIG. 14 is a diagram of an example of the data type conversion throughthe inheritance depicted in FIG. 13. In FIG. 14, date-type data“20090526” defined in the conversion source 101 (From side) is convertedinto an integer “20,090,526” by the data type converting process(character→integer conversion) “character-to-integer conversion”inherited from the character string type of the Supertype.

FIG. 15 is a diagram of an example of the cleansing specificationdefinition file 301 that describes the inheritance relationship betweenthe Supertype (Char type) and the Subtype (date type) depicted in FIG.13. Since <DTCV_RULE> tag indicative of the data type conversion is notdefined for the date type, the next data type converting functiondefined for the character string type (Char) of the Supertype is inheritand applied. Specifically, the data of the date type is handled as thatof the Char type to apply the data type converting function:character-to-integer conversion defined for the Char type to the datatype conversion from the date type to the Integer type and to apply thedata type converting function: integer-to-character conversion definedfor the Integer type to the data type conversion from the Integer typeto the date type.

As a result, the data type conversion with the existing data typenecessitated by the addition of data type may be reduced to therequisite minimum. Therefore, the cost of the addition of data type isreduced and the prevention of the contradiction to the data typeconversion may be achieved at the same time.

Description will be made of an example of defining a default value for atype attribute value to simplify the meta-definition file 304. If thenumber of the type attributes increases, the operation of specifying allthe type attributes defined for all the items of the meta-definitionfile 304 becomes problematic. By specifying a default value through adefault attribute in the definition of the type attributes in thecleansing specification definition file 301, it may be considered that adefault value is set as a value of a type attribute not defined as anitem of the meta-definition file 304. This enables the simplification ofthe meta-definition file 304.

FIG. 16 is a diagram of one description example of the cleansingspecification definition file 301 with default values defined as typeattributes. In FIG. 16, as indicated by an underscored portion, defaulttype attribute values are described as the definitions of the typeattributes in such a way as “default=“JEF””, “default=“20””, and“default=“Yes””.

FIG. 17 is an exemplary diagram of the simplification of themeta-definition file 304. In FIG. 17, the upper meta-definition file 304is a description example before the simplification and the lowermeta-definition file 304 is a description example after thesimplification of the meta-definition file 304 based on the cleansingspecification definition file 301 depicted in FIG. 16.

Referring to the meta-definition file 304 before the simplification ofFIG. 17, the type attributes of the data type: personal name type forthe column name “FULL_NAME” include the type attribute: character codesystem (char_code) and “JEF” is defined as the type attribute valuethereof. The type attributes of the data type: character string type forthe column name “TELEPHONE_NUMBER” include the type attribute: charactercode system and “JEF” is defined as the type attribute value thereof.Since “JEF” is defined as the default type attribute value of the typeattribute: character code system in FIG. 16, the description of the typeattribute: character code system may be skipped in the meta-definitionfile 304.

Referring to the meta-definition file 304 before the simplification ofFIG. 17, the type attributes of the data type: personal name type forthe column name “FULL_NAME” include the type attribute: maximumcharacter string length (max_length) and “20” is defined as the typeattribute value thereof. The type attributes of the data type: characterstring type for the column name “TELEPHONE_NUMBER” include the typeattribute: maximum character string length and “20” is defined as thetype attribute value thereof. Since “20” is defined as the default typeattribute value of the type attribute: maximum character string lengthin FIG. 16, the description of the type attribute: maximum characterstring length may be skipped in the meta-definition file 304.

Referring to the meta-definition file 304 before the simplification ofFIG. 17, the type attributes of the data type: personal name type forthe column name “FULL_NAME” include the type attribute:first/second-name space (name_space) and “Yes” is defined as the typeattribute value thereof. Since “Yes” is defined as the default typeattribute value of the type attribute: first/second-name_space in FIG.16, the description of the type attribute: first/second-name_space maybe skipped in the meta-definition file 304.

A function of the cleansing processing unit 312 depicted in FIG. 3A willbe described in detail. As described above, the cleansing processingunit 312 refers to the conversion rule set 330 through the cleansingcontrol unit 351 to control the type conversion calling unit 352 and thecleansing calling unit 353. Specifically, the cleansing control unit 351determines which type converting process is to be executed and drivesthe type conversion calling unit 352 to call the determined typeconverting process from the type converting function library 302.Similarly, the cleansing control unit 351 determines which cleansingprocess is to be executed and drives the cleansing calling unit 353 tocall the determined cleansing process from the cleansing functionlibrary 303. The expansion of the cleansing interface for the cleansingcalling unit 353 and the cleansing function will first be described.

FIG. 18 is a diagram of an exemplary cleansing function. The cleansingfunction is a function of converting an input From value to output thevalue as a To value and the cleansing function is uniquely determinedbased on the cleansing rule table 332 and called by the cleansingcalling unit 353 under the control of the cleansing control unit 351.

For example, in the cleansing specification definition file 301 depictedin FIG. 5, the type attribute: character code system (char_code) isdefined for the data type: character string type (Char) as the data typeand “SJIS”, “JEF”, and “UTF8” (JEF) are usable as the type attributevalue thereof. The character code system converting function isspecified as the cleansing rule (CL_RULE). The character code systemconversion in this case is prescribed with “from=“*””, which is theoperation condition on the From side (the conversion source 101), and“to =“*””, which is the operation condition on the To side (theconversion destination 102), and is defined as a function of executingthe necessary conversion between the character code systems according toa combination of arbitrary type attribute values of the char_code typeattribute defined in advance.

The cleansing interface is configured to input the type attribute valuesof the From side and the To side as “From definition” and “Todefinition” to the cleansing function as depicted in FIG. 18 so as tosupport such a cleansing function having multiple conversion patterns.

For example, in regard to the character code system cleansing process inthe mapping definition of (1), which correlates the item of“EMPLOYEE_NUMBER” of the TABLE_A with “EMPLOYEE_NUMBER” of the TABLE_Bin the meta-definition file 304 depicted in FIG. 8, “JEF” is deliveredas the character code system of the item “EMPLOYEE_NUMBER” of theTABLE_A, which is the conversion source, for the “From definition” alongwith the From value from the cleansing control unit 351, and “SJIS” isdelivered as the character code system of the item “EMPLOYEE_NUMBER” ofthe TABLE_B, which is the conversion destination, for the “Todefinition” from the cleansing control unit 351 to the cleansingfunction as depicted in FIG. 18.

When receiving the “From definition”, the “From value”, and the “Todefinition”, the cleansing function recognizes from the “Fromdefinition” and the “To definition” that the character code systemconversion from “JEF” to “SJIS” is necessary, considers a value of the“From value” as a JEF character string to execute the conversion to acharacter string of Shift JIS (SJIS), and outputs the conversion resultto the “To value”. This arrangement is able to implement the cleansingfunction supporting multiple conversion patterns determined according tothe combination of the “From definition” and the “To definition”.

Description will be made of an example of making the implementation ofthe cleansing function easier or enabling an advanced cleansing functionto be implemented by delivering the data type and all the type attributevalues defined for the data item to be converted as the from definitionand the To definition to the cleansing function in addition to thespecification expansion depicted in FIG. 18 with reference to FIG. 19.

FIG. 19 is another explanatory diagram of an exemplary cleansingfunction. FIG. 19 depicts an example of executing a length adjustingfunction that is a function of adjusting a total length of a characterstring as the next cleansing function after the character code systemconverting process depicted in FIG. 18 is completed for the mappingdefinition of (1) defined in the meta-definition file 304 depicted inFIG. 8. The cleansing control unit 351 delivers the data type: characterstring type (Char), the type attribute: character code system(char_code) and the type attribute value: JEF, and the type attribute:maximum character string length (max_length) and the type attributevalue: 20 as the From definition. In this way, the data type and all thetype attributes and the type attribute values are delivered.

Similarly, for the To definition, the cleansing control unit 351delivers the data type: character string type (Char), the typeattribute: character code system (char_code) and the type attributevalue: JEF, and the type attribute: maximum character string length(max_length) and the type attribute value: 14 as the To definition. Inthis way, the data type and all the type attributes and the typeattribute values are delivered.

Therefore, if the character string of the From value concurrentlydelivered from the cleansing control unit 351 is within 14 bytes, thevalue is directly copied to the To value in the length adjustingfunction. On the other hand, if the character string of the From valueexceeds 14 bytes, the value is copied to the To value with a portionafter the 14th byte cut off. When a character string is cut off, thechar_code type attribute is referenced and if the value is cut at themiddle of a mutibyte character, the cutting may be made before themutibyte character to prevent undesirable separation of a character.Alternatively, the correct number of characters may be measured byreferring to the char_code type attribute to implement the lengthadjusting function for management using the number of characters.

Description will be made of an example of reflecting a state of aprocess result on the From definition by the cleansing function inaddition to the specification expansion depicted in FIG. 19 withreference to FIG. 20.

FIG. 20 is another explanatory diagram of an exemplary cleansingfunction. FIG. 20 depicts an example of executing the character codesystem converting process depicted in FIG. 18 and the length adjustingfunction depicted in FIG. 19 by using a mode with specification expandedso as to enable more efficient cleansing control for the mappingdefinition of (1) defined in the meta-definition file 304 depicted inFIG. 8. On the left side of FIG. 20, the cleansing process for thechar_code type attribute is executed. The data type: character stringtype (Char), the type attribute: character code system (char_code) andthe type attribute value: JEF, and the type attribute: maximum characterstring length (max_length) and the type attribute value: 20 are given tothe cleansing function: character code system conversion as the Fromdefinition. Similarly, the data type: character string type (Char), thetype attribute: character code system (char_code) and the type attributevalue: SJIS, and the type attribute: maximum character string length(max_length) and the type attribute value: 14 are given as the Todefinition.

If the From value conforming to the From definition is given to thecleansing function in this state, the character code system of the Fromvalue is converted from JEF to SJIS. The cleansing function copies theconversion result to the To value and updates the type attribute value:JEF of the From definition to the process result, i.e., SJIS of the Todefinition.

On the right side of FIG. 20, the cleansing process for the max_lengthtype attribute is executed as the process of the next stage. The Fromdefinition updated in the process of the preceding stage (the left sideof FIG. 20) is directly given as the From definition to the cleansingfunction: length adjusting function. Similarly, the data type: characterstring type (Char), the type attribute: character code system(char_code) and the type attribute value: SJIS, and the type attribute:maximum character string length (max_length) and the type attributevalue: 14 are given as the To definition.

If the From value conforming to the From definition is given to thecleansing function in this state, the maximum character string length ofthe From value is adjusted from 20 bytes to 14 bytes. The cleansingfunction copies the conversion result to the To value and updates thetype attribute value: 20 (bytes) of the From definition to the processresult, i.e., 14 (bytes) of the To definition. Since this causes theFrom definition to have the same contents as the To definition, theprocess is terminated.

By reflecting the state of the process result on the From definition,the From definition may directly be input to the next cleansing process(the process on the next stage) that processes the same value to deliverthe state of the value to be input and, therefore, the overall processefficiency is increased and the process on the next stage becomes moreaccurate since the From definition accurately reflects the state of theFrom value. Although the To definition may directly be delivered to thenext stage, the To value of the preceding stage must be delivered as theFrom value of the next stage.

The execution order of the cleansing function will be described. In thisembodiment, the execution order of the cleansing function is set to adefined order such that the function is executed in the order from moreimportant type attributes. Specifically, if the cleansing functioncorresponding to multiple type attributes is executed for one value, thefunction is executed in the order from the type attributes definedpreviously. As a result, since the cleansing is executed in the orderfrom a more important type attribute, the occurrence of uselessprocesses may be prevented and the cleansing process may be simplified.

FIG. 21 is a chart of the execution order of the cleansing function.FIG. 21 depicts the execution order in an example of cleansing of aFULL_NAME that is the mapping definition (2) of the meta-definition file304 depicted in FIG. 8 based on the cleansing specification definitionfile 301 depicted in FIG. 6. In the cleansing of the FULL_NAME of FIG.8, the char_code type attribute is defined before the max_length typeattribute in the cleansing specification definition file 301 of FIG. 6.

In the process of the data type, the type conversion is not necessarysince both the From side and the To side are the character string type(Char type). Since the data type conversion is performed before thecleansing process, the data types are the same in the cleansing process.

In the process of the type attribute: character code system (char_code),the character code system of the meta-defined FULL_NAME is subjected tothe character code system conversion from the type attribute value: JEFof the From side into the type attribute value: SJIS of the To side. Thelength adjustment is performed by setting the maximum character stringlength from 20 to 14 for the FULL_NAME having the type attribute valueSJIS after the process of the character code system (char_code). Asdescribed, the type attributes of important (basic) property are definedand executed earlier.

Therefore, the process may be executed on the basis that the typeattributes that are more important (higher) than the type attribute ofinterest are identical. It is not necessary to give consideration to thetype attribute lower than the type attribute of interest. The order ofthe process is maintained constant and the process is simplified.

An exemplary implementation of the cleansing function corresponding tomultiple type attributes will be described. By implementing thecleansing function capable of supporting multiple type attributes, acombination of the type attributes and the cleansing function becomesflexible. Therefore, a more advanced cleansing function may be realizedand the number of times of execution of the cleansing process may bereduced, contributing to performance improvement.

FIG. 22 is a diagram of an example of the cleansing specificationdefinition file 301 that defines the cleansing function corresponding tomultiple type attributes. In FIG. 22, a cleansing function “charactercode system conversion” is defined with two type attributes of acharacter code system (char_code) and an external character code system(char_excode), which forms the cleansing function corresponding to theboth type attributes. The external character code system is a systemthat specifies external character systems when multiple externalcharacter systems (external character code 1, external character code 2)are handled, and is a type attribute added as the expansionspecification of the character code system.

FIG. 23 is a diagram of the cleansing function that executes bothprocesses for the character code system (char_code) and the externalcharacter code system (char_excode) defined in FIG. 22. In FIG. 23, thecleansing function executes the character code system conversion. In thecharacter code system conversion, the cleansing process for thechar_excode type attribute is executed along with the cleansing processfor the char_code type attribute.

Specifically, the data type: character string type (Char), the typeattribute: character code system (char_code) and the type attributevalue: JEF, and the external character code system (char_excode) and thetype attribute value: external character code 1, and the type attribute:maximum character string length (max_length) and the type attributevalue: 20 are given as the From definition. Similarly, the data type:character string type (Char), the type attribute: character code system(char_code) and the type attribute value: SJIS, and the externalcharacter code system (char_excode) and the type attribute value:external character code 2, and the type attribute: maximum characterstring length (max_length) and the type attribute value: 14 are given asthe To definition.

If the From value conforming to the From definition is given to thecleansing function: character code system conversion in this state, thecleansing function: character code system conversion converts thecharacter code system of the From value from JEF to SJIS. The cleansingfunction: character code system conversion also converts the externalcode system of the From value from external character code 1 to externalcharacter code 2.

By executing the conversions corresponding to different type attributes,i.e., the character code system conversion and the external charactercode system conversion in one type attribute conversion with onecleansing function as above, the number of times of execution may bereduced (from two times to one time in this example). In this case, thelength adjustment is executed as the cleansing function in the processof the next stage.

The higher-speed processing in the cleansing processing unit 312 will bedescribed. In this description, the data converting process will bedescribed with reference to the cleansing specification definition file301 of FIG. 25 and the meta-definition file 304 of FIG. 24.

FIG. 24 is a diagram of an example of the meta-definition file 304. Inthe higher-speed processing, the meta-definition file 304 is optimizedbefore the start of the integration process (at the time ofinitialization) to a state that enables a higher-speed process anddeployed on the RAM 203 or the ROM 202 as the encoded meta-definitioninformation 340 as described later in FIG. 44.

FIG. 25 is a diagram of an example of the cleansing specificationdefinition file 301. The data types defined in FIG. 25 are described inthe order of definition of the Char type (character string type), thepersonal name type, an address type, and the integer type (integertype). The cleansing specification definition file 301 is put into theoptimized state by assigning type IDs unique in the entire dataconverting apparatus 300 before the initialization of themeta-definition file 304 and is deployed on the RAM 203 or the ROM 202as the conversion rule set 330 as described later in FIGS. 26 to 46.

FIG. 26 is a diagram of the data type code table 321. In the data typecode table 321, the type IDs are those transforming the data types intoIDs and are consecutive integers starting from one in the order ofdefinition of the data types defined in the cleansing specificationdefinition file 301.

Similarly, the type attributes defined in the cleansing specificationdefinition file 301 are transformed into IDs by assigning type attributeIDs that are unique in their respective data types and that are the samefor the inherited type attributes between the data types in theinheritance relationship. Although the type attribute code table 322 ofthe Char type is included in the data types of the Supertype in thisdescription, the table may be configured as the independent typeattribute code table 322.

FIGS. 27 to 29 are explanatory diagrams of the type attribute codetables 322. FIG. 27 is the type attribute code table 322 of the Char(character string type) and the personal name type; FIG. 28 is the typeattribute code table 322 of the Char (character string type) and theaddress type; and FIG. 29 is the type attribute code table 322 of theInteger (integer type).

In the type attribute code tables 322 depicted in FIGS. 27 to 29, thetype IDs are consecutive integers for the data types starting from onein the order of definition of the data types described in the cleansingspecification definition file 301. To the type attributes of the datatype having the inheritance relationship, the IDs are assigned insequence from the type attribute of the data type having the oldestancestor. Therefore, the type attribute IDs having a common ancestor arematched.

For example, since the personal name type inherits the Char type in FIG.27, the type attribute IDs: 1 to 3 of the Char type, i.e., the ancestorof the personal name type are matched. Similarly, since the address typeinherits the Char type in FIG. 28, the type attribute IDs: 1 to 3 of theChar type, i.e., the ancestor of the address type are matched.

Similarly, the type attribute values defined in the cleansingspecification definition file 301 are assigned with the type attributevalue IDs unique in respective type attributes.

FIGS. 30 to 35 are explanatory diagrams of the type attribute value codetables 323. FIG. 30 is the type attribute value code table 323 with thetype attribute IDs assigned to the type attribute values of thechar_code type attribute. FIG. 31 is the type attribute value code table323 with the type attribute IDs assigned to the type attribute values ofthe char_excode type attribute. FIG. 32 is the type attribute value codetable 323 with the type attribute IDs assigned to the type attributevalues of the name_space type attribute. FIG. 33 is the type attributevalue code table 323 with the type attribute IDs assigned to the typeattribute values of the chou_banchi type attribute.

In the type attribute value code tables 323 depicted in FIGS. 30 to 33,the type attribute value IDs are assigned to the type attributes and areconsecutive integers starting from zero in the order of definition ofthe type attributes. An undefined type attribute value is assigned with“−1” as the type attribute value. In FIGS. 30 to 33, a type attributevalue having “*” is a type attribute value under the declaration ofdefault (default value).

FIG. 34 depicts the type attribute value code table 323 of themax_length type attribute. FIG. 35 depicts the type attribute value codetable 323 of the max_digit type attribute. As depicted in FIGS. 34 and35, in the case of the type attribute having no type attribute valuedefined in the cleansing specification definition file 301 and having anarbitrary type attribute value, the type attribute value defined in themeta-definition file 304 is directly used as the type attribute valueID.

A data type conversion rule will be described. A data type conversionrule is a conversion rule table that determines the execution patternsof the function of converting data to be converted from the data type ofthe From side (the conversion source 101) to the data type of the Toside (the conversion destination 102).

FIG. 36 is a diagram of the data type conversion rule table 331. In FIG.36, the data type conversion rule table 331 is configured with the datatype IDs arranged at From/To to determine the converting function to beexecuted according to the combinations thereof. Specifically, a link toa type converting function existing in the type converting functionlibrary 302 (a calling pointer to a type converting function) is set asa value of the data type conversion rule table at a position of thecombination of the corresponding data type IDs.

A copy function of simply duplicating a value is set for the combinationof From/To without the need for conversion (described as “Copy” in thecorresponding columns of FIG. 36). For the inherited data typeconverting function, the function defined in the data type of the mostrecent ancestor is employed. “0” at From/To is used as the meaning of“data type ID undefined”, and a combination of the same data type IDs atFrom/To is not used and is left blank.

Similarly, for the type attribute values, a conversion rule is definedfor each type attribute as a cleansing rule. The cleansing rule is aconversion rule table that determines the execution patterns of thefunction of converting data to be converted from the type attribute ofthe From side (the conversion source 101) to the type attribute of theTo side (the conversion destination 102).

FIGS. 37 to 42 are explanatory diagrams of cleansing rule tables 332.The cleansing rule table 332 of FIG. 37 is a cleansing rule for thechar_code type attribute. The cleansing rule table 332 of FIG. 38 is acleansing rule for the char_excode type attribute. The cleansing ruletable 332 of FIG. 39 is a cleansing rule for the name_space typeattribute.

The cleansing rule table 332 of FIG. 40 is a cleansing rule for thechou_banchi type attribute. The cleansing rule table 332 of FIG. 41 is acleansing rule for the max_length type attribute. The cleansing ruletable 332 of FIG. 42 is a cleansing rule for the max_digit typeattribute.

In FIGS. 37 to 40, the cleansing rule table 332 is configured with thetype attribute value IDs arranged at From/To to determine the cleansingfunction to be executed according to the combinations thereof.Specifically, a link to a cleansing function existing in the cleansingfunction library 303 (a calling pointer to a cleansing function) is setas a value of the cleansing rule table 332 at a position of thecombination of the corresponding type attribute value IDs.

A copy function of simply duplicating a value is set for the combinationof From/To without the need for conversion. A combination of the sametype attribute value IDs at From/To is not used and is left blank.Different cleansing functions may be defined according to thecombinations of From/To.

As depicted in FIGS. 41 and 42, a type attribute having an arbitraryvalue does not selectively use the cleansing functions and therefore hasone cleansing function. Therefore, a link is set to the cleansingfunction corresponding to the coordinates 0:0 of From/To.

A process of organizing the data type conversion rule table 331 and thecleansing rule table 332 is then executed. Specifically, for example,the conversion rule set 330 is established that may directly bereferenced from the data type IDs, the type attribute IDs, and the typeattribute value IDs.

FIG. 45 is a diagram of the conversion rule set 330. The conversion ruleset 330 is made up of a conversion rule table 4300 and conversion ruletables for data type 4301 to 4304. The conversion rule table 4300 is atable for referencing the data type conversion rule table correspondingto the relevant data type by referencing a data type ID as the sequencenumber.

Specifically, the sequence number [0] is left blank and the sequencenumber [1 and thereafter] is matched with the data type ID. The datatypes described in the conversion rule table 4300 are actually linked byassigning respective conversion rule tables for data type 4301 to 4304(entering the calling pointers to the corresponding tables).

The conversion rule tables for data type 4301 to 4304 are generated forthe respective data types and are tables for referring to the data typeconversion rule table including the corresponding data type as theconversion source through the sequence number [0] and for referring to atype attribute ID as the sequence number to refer to the cleansing ruletable corresponding to the relevant type attribute.

Specifically, the sequence number [0] of the conversion rule tables fordata type is assigned with the data type conversion rule table 331 andthe sequence number [1 and thereafter] is assigned with the cleansingrule table 332 corresponding to the matching type attribute ID.

For example, for the Char type of the data type ID: 1, the conversionrule table for the Char type 4301 is set at the sequence number [1] ofthe conversion rule 4300. In the conversion rule table for the Char type4301, a pointer is set at the sequence number [0] to the data typeconversion rule table 331 depicted in FIG. 36; a pointer is set at thesequence number [1] to the cleansing rule table 332 (FIG. 37) for thechar_code type attribute having the type attribute ID: 1; a pointer isset at the sequence number [2] to the cleansing rule table 332 (FIG. 38)for the char_excode attribute having the type attribute ID: 2; and apointer is set at the sequence number [3] to the cleansing rule table332 (FIG. 34) for the max_length type attribute having the typeattribute ID: 3.

A process of encoding the meta-definition file 304 to create the encodedmeta-definition 340 will be described. In this description, themeta-definition file 304 depicted in FIG. 24 is taken as an example. Theitem definitions in the meta-definition file 304 are encoded by usingthe IDs (the data type IDs, the type attribute IDs, and the typeattribute value IDs) assigned through the initialization of thecleansing specification definition file 301. In the meta-definition file304 of FIG. 4, employee numbers, full names, addresses, and telephonenumbers are defined in the TABLE_A (physical model) and the TABLE_B(logic model) as the item definitions. Therefore, each item definitionis encoded for each table.

FIG. 44 is a diagram of the encoded meta-definition information 340corresponding to FIG. 24. The encoded meta-definition information 340 isconfigured to simplify the reference to the conversion rule tables fordata type by creating an item meta-definition table corresponding to theitem definitions defined by <COLUMN> tags in the meta-definition file304 and giving the same structure to the property of each item as theconversion rule tables for data type in the conversion rule set 330.Specifically, the sequence number [0] of the item meta-definition tableis configured to be the data type ID and the sequence number [1 andthereafter] is configured to be the type attribute value ID when thesequence number is assumed to be the type attribute ID. An arrow betweenthe item meta-definition tables represents the mapping definitiondefined by the <MAP_RULE> tag in the meta-definition file 304 and, ifthe data conversion is performed from the TABLE_A to the TABLE_B, thestart end of the arrow indicates the From side (conversion source) andthe terminal end indicates the To side (conversion destination).

In FIG. 44, (A) depicts the encoded meta-definition information 340 ofthe TABLE_A that is the data model on the From side and the TABLE_B thatis the data model on the To side for EMPLOYEE_NUMBER. (B) in FIG. 44depicts the encoded meta-definition information 340 of the TABLE_A thatis the data model on the From side and the TABLE_B that is the datamodel on the To side for the FULL_NAME. (C) in FIG. 44 depicts theencoded meta-definition information 340 of the TABLE_A that is the datamodel on the From side and the TABLE_B that is the data model on the Toside for the addresses. (D) in FIG. 44 depicts the encodedmeta-definition information 340 of the TABLE_A that is the data model onthe From side and the TABLE_B that is the data model on the To side forTELEPHONE_NUMBER.

For example, taking the FULL_NAME in the TABLE_A depicted in FIG. 44B asan example, the sequence number [0] is set for the data type ID: 2 ofthe personal name type (see FIG. 26) defined as the data type of theFULL_NAME item of the TABLE_A. The sequence number [1] is set for thetype attribute value ID: 1 of the type attribute value: JEF (see FIG.30) of the char_code type attribute (see FIG. 27) having the sequencenumber [1] as the type attribute ID for the type attribute defined forthe FULL_NAME item of the TABLE_A. Similarly, the sequence number [2] isset for the type attribute value ID: 0 of the type attribute value:external character code 1 (see FIG. 31) of the char_excode typeattribute (see FIG. 27) having the type attribute ID: 2. Similarly, thesequence number [3] is set for the type attribute value: 20 (see FIG.41) of the max_length type attribute (see FIG. 27) having the typeattribute ID: 3. Similarly, the sequence number [4] is set for the typeattribute value ID: 0 of the type attribute value: Yes (see FIG. 32) ofthe name_space type attribute (see FIG. 27) having the type attributeID: 4. As in the case of the max_length type attribute in theTELEPHONE_NUMBER item of the TABLE_A, if the type attribute value is notdefined in the meta-definition file 304 and the default value is notdefined in the cleansing specification definition file 301, “−1” is set.

As described, in the encoded meta-definition information 340, the datatype ID of the item is set for the item number [0] of the itemmeta-definition table, and the type attribute value IDs having the itemnumbers as the type attribute ID are sequentially set from the itemnumber [1]. This enables efficient checking of the conversion rule set330 deployed based on the cleansing specification definition file 301. Adata conversion example using the encoded meta-definition information340 related to a FULL_NAME in the TABLE_A and the TABLE_B depicted inFIG. 44B will be described. It is assumed that “YAMADA KAZUO” is thedata to be converted that is a value of the FULL_NAME in the TABLE_A.

FIGS. 45 to 49 are explanatory diagrams of a first data conversionexample using the encoded meta-definition information 340 related to theFULL_NAME in the TABLE_A and the TABLE_B depicted in FIG. 44. Encodingconsistent in the entire system is performed as described above inadvance through the initializing process and the processes may beexecuted by using the codes (which means that the meanings arerecognized in the processes). In the data converting process of thecleansing processing unit, the cleansing control unit 351 is given anitem meta-definition table and a value related to the item to beconverted depicted in FIG. 45 to start the converting process.

In the converting process, the data types are compared between the Fromside and the To side. The values of the sequence number [0] is comparedbetween the encoded meta-definition information 340 of the From side andthe encoded meta-definition information 340 of the To side. In thiscase, the both values are “2” indicative of the data type ID: 2(personal name type) and recognized as the same data type.

Since the data types are the same, the type attributes are then comparedbetween the From side and the To side. A comparison is made between thevalues of the sequence number [1], which is the type attribute at thehead. Since the values are “1” (JEF) on the From side and “0” (SJIS) onthe To side in FIG. 45, the converting process is specified according tothe conversion rule set 330 of FIG. 43.

Specifically, the conversion rule table 4300 is referenced according tothe sequence number [2] because of the data type ID: 2 (personal nametype) to make a reference to the conversion rule table for personal nametype 4302.

A reference is then made to the cleansing rule table for char_code 332(FIG. 37) of the sequence number [1] currently compared in theconversion rule table for personal name type 4302. Since the typeattribute value ID of the From side is “1” (JEF) and the type attributevalue ID of the To side is “0” (SJIS), the IDs are used as the sequencenumbers to make a reference to the cleansing rule table for char_code332 of FIG. 37 to specify the calling pointer to the “character codesystem conversion”. These processes may be processed at one time with aprogramming language (e.g., C language) to achieve high-speed operationas follows.

converting process=conversion rule [data type ID]→rule [type attributeID]→cleansing rule [type attribute value ID of From side] [typeattribute value ID of To side]

Since the “character code system conversion” is specified as thecleansing function as above, the “character code system conversion”described with reference to FIG. 23 is executed to convert the charactercode system (char_code) and the external character code system(char_excode) at the same time and the conversion result is set in theFrom definition and the To value. As a result, the values of thesequence numbers [1] and [2] of the encoded meta-definition information340 related to the FULL_NAME in the TABLE_A are updated with “0” (SJIS)and “1” (external character code 2) as depicted in FIG. 46. The value ofthe FULL_NAME in the TABLE_B is correspondingly set to “YAMADA KAZUO” asa value using the external character code 2 in SJIS.

The type attribute value IDs set for the next sequence number [2] issimilarly compared for the meta-definition of FIG. 46. Since the bothtype attribute value IDs are “1” (external character code 2), a shift ismade to the next sequence number [3].

In comparison of the type attribute value IDs of the sequence number[3], the FULL_NAME in the TABLE_A has “20” and the FULL_NAME in theTABLE_B has “14”. Since the values are different from each other, aconverting process is specified.

Specifically, the cleansing rule table is referenced for max_length 332of the sequence number [3] in the conversion rule tables for personalname type 4302 currently compared. Since the cleansing rule table formax_length 332 (see FIG. 41) uses an arbitrary type attribute value, the“length adjustment” is specified as the cleansing function having “0”defined for both the From side and the To side. Therefore, the “lengthadjustment” is called. The To value of the previous process result isset as the From value to execute the “length adjustment”. FIG. 47depicts the execution of the “length adjustment” function and FIG. 48depicts the result. Specifically, if the character string length of theFrom value exceeds 14 bytes, the length is adjusted to 14 bytes.

In FIG. 48, since the “length adjustment” is executed, the sequencenumber [3] of the From definition is updated with the type attributevalue of the conversion result (value of the sequence number [3] of theTo definition). Specifically, the value of the sequence number [3] ofthe meta-definition related to the FULL_NAME in the TABLE_A is updatedfrom “20” to “14”. Subsequently, the “first/second-name spacing process”is specified by performing the same operation for the next sequencenumber [4] and the value of the From definition is update with the typeattribute value after the conversion (see FIG. 49).

As a result, the values of all the sequence numbers are matched in theencoded meta-definition related to the FULL_NAME in the TABLE_A that isthe From definition and the encoded meta-definition related to theFULL_NAME in the TABLE_B that is the To definition. Since all arematched as above, the converting process is terminated. The high-speeddata conversion may be implemented by repeatedly comparing the values ofthe From definition sequentially from the left to specify and executethe processes if the values are different.

The data converting process procedure of the data converting apparatus300 according to the second embodiment will be described with referenceto FIGS. 50 to 54.

FIG. 50 is a flowchart of the data converting process procedure of thedata converting apparatus 300 according to the first embodiment. First,the initializing unit 311 executes the initializing process (stepS5001). Details of the initializing process (step S5001) will bedescribed with reference to FIGS. 51 and 52.

The cleansing processing unit 312 executes the data converting process(step S5002). Details of the data converting process (step S5002) willbe described with reference to FIG. 54. It is then determined whetherthe data conversion is to be continued (step S5003). The criterion maybe operational input from a user or the presence of data to beconverted.

If continued (step S5003: YES), the procedure proceeds to step S5002 toexecute the data converting process. On the other hand, if not continued(step S5003: NO), a release process is executed (step S5004). In therelease process, a resource on the memory obtained at the initializingprocess (step S5001) is released. This leads to termination of the dataconverting process.

FIG. 51 is a flowchart of a process procedure (first half) of theinitializing process (step S5001) executed by the initializing unit 311depicted in FIG. 50. As depicted in FIG. 51, the cleansing specificationdefinition file 301 is read and analyzed (step S5101). A data type codetable creating process is then executed (step S5102). Specifically, datatype IDs are added to the data types. For example, as depicted in FIG.26, entirely unique integers starting from one are added as the datatype IDs consecutively without a skip in the order of definition.

A type attribute code table creating process is executed (step S5103).Specifically, type attribute IDs are added to the type attributes. Forexample, as depicted in FIGS. 27 to 29, integers unique within a datatype starting from one consecutively without a skip in the order ofdefinition are added as the type attribute IDs to all the typeattributes in the order from the data type of the ancestor. Between thedata types having the inheritance relationship, the type attribute IDsof common type attributes are controlled to be consistent in the entiresystem.

A type attribute value code table creating process is executed (stepS5104). Specifically, as depicted in FIGS. 30 to 35, type attributevalue IDs are added to the type attribute values. The details of thetype attribute value code table creating process (step S5104) aredescribed with reference to FIG. 53.

After the type attribute value code table creating process (step S5104),as depicted in FIG. 36, the data type conversion rule table 331 isgenerated (step S5105). As depicted in FIGS. 37 to 42, the cleansingrule table 332 is generated (step S5106). Subsequently, as depicted inFIG. 43, the conversion rule table 331 and the cleansing rule table 332are combined as a conversion rule set 330 and the procedure proceeds tostep S5201 of FIG. 52.

FIG. 52 is a flowchart of a process procedure (second half) of theinitializing process (step S5001) executed by the initializing unit 311depicted in FIG. 50. After the cleansing rule set 330 is built, in FIG.52, the meta-definition file 304 is then read and analyzed (step S5201).The types of analyzed information are sequentially determined (stepS5202). Specifically, it is determined whether the information is a datatype, a type attribute, or a type attribute value. The determination ismade according to the order of description in the meta-definition file304.

In the case of the data type (step S5202: DATA TYPE), the data type istransformed into ID (step S5203). Specifically, the data type code table321 (FIG. 26) is referenced for the transformation into the data typeID. The procedure proceeds to step S5208.

If the type of the information is a type attribute (step S5202: TYPEATTRIBUTE), the type attribute is transformed into ID (step S5204).Specifically, the type attribute code table 322 (FIGS. 27 to 29) isreferenced for the transformation into the type attribute ID. Theprocedure proceeds to step S5208.

If the type of the information is a type attribute value (step S5202:TYPE ATTRIBUTE VALUE), it is determined whether the type attribute valueis encoded (step S5205). If the type attribute value is encoded (stepS5205: YES), the type attribute value code table 323 (FIGS. 30 to 35) isreferenced for the transformation into the type attribute value ID (stepS5206). The procedure proceeds to step S5208.

If the type attribute value is not encoded (step S5205: NO), an integervalue of the type attribute value is directly defined as the typeattribute value ID (step S5207). The procedure proceeds to step S5208.

At step S5208, as depicted in FIG. 44, the item definition of datamodels in the meta-definition file 304 is encoded to create the itemmeta-definition table (step S5208). Specifically, the sequence number[0] is set for the data type ID and the sequence numbers [1], [2], [3],. . . are set for the type attribute value IDs or the type attributevalues (if not encoded) of the type attribute having the type attributeIDs identical to the sequence numbers. For example, if the itemmeta-identification table having the data model related to the employeeitem of the TABLE_A is created, the sequence number [0] is set for thedata type ID: 4 (see FIG. 26) indicative of the integer type that is thedata type of the EMPLOYEE_NUMBER item and the sequence number [1] is setfor the type attribute value: 12 (see FIG. 35) of the max_digit typeattribute (see FIG. 29) that is the type attribute ID: 1 of the integertype as depicted in FIG. 44. Since the type attribute value of themax_digit type attribute is a type attribute value not encoded, the typeattribute value: 12 specified in the meta-definition file 304 isdirectly used for the setting.

It is then determined whether all the data models in the meta-definitionfile 304 have been encoded (step S5209). If not all the data models areencoded (step S5209: NO), the procedure returns to step S5202 to encodethe remaining data models. On the other hand, if all the data models areencoded (step S5209: YES), the encoded meta-definition information 340is configured as a group of encoded item meta-definition as depicted inFIG. 44 (step S5210). Subsequently, a shift is made to the dataconverting process (step S5002).

FIG. 53 is a flowchart of a process procedure of the type attributevalue code table creating process (step S5104) depicted in FIG. 51. Anunselected type attribute is pointed to in the cleansing specificationdefinition file 301 (step S5301). It is determined whether a typeattribute value is defined for the pointed type attribute (step S5302).If the type attribute value is defined (step S5302: YES), type attributevalue IDs are added to all the type attribute values defined as the typeattribute values of the pointed type attribute (step S5303).Specifically, integers unique within the type attribute are added as thetype attribute value IDs starting from zero consecutively without a skipin the order of definition for each type attribute. The procedureproceeds to step S5305.

On the other hand, if no type attribute value is defined (step S5302:NO), the meta-definition file 304 for the undefined type attribute valueis referenced and if all the type attribute values are integer valuesusable directly as the type attribute values for the relevant typeattribute, the type attribute values defined in the meta-definition file304 are directly used as the type attribute value IDs. If other valuesexist, integers unique within the type attribute are added as the typeattribute value IDs starting from zero consecutively without a skip(step S5304). The procedure proceeds to step S5305.

At step S5305, it is determined whether an unselected type attribute ispresent (step S5305). If an unselected type attribute is present (stepS5305: YES), the procedure returns to step S5301. On the other hand, ifno unselected type attribute is present (step S5305: NO), the procedureproceeds to step S5105 of FIG. 51 to generate the data type conversionrule table 331.

FIG. 54 is a flowchart of a process procedure of the data convertingprocess (step S5002) depicted in FIG. 50. It is determined whether anunselected pair of the encoded meta-definition information 340 ispresent (step S5401). If an unselected pair of the encodedmeta-definition information 340 is present (step S5401: YES), theunselected pair of the encoded meta-definition information 340 isselected (step S5402).

A pair of the encoded meta-definition information 340 is a combinationof the encoded meta-definition information 340 of the From side and theencoded meta-definition information 340 of the To side corresponding tothe encoded meta-definition information 340. For example, in the exampleof FIG. 44, if it is assumed that the encoded meta-definitioninformation 340 related to the FULL_NAME in the TABLE_A on the From sideis the encoded meta-definition information 340 of the From side, theencoded meta-definition information 340 related to the FULL_NAME in theTABLE_B on the To side is the corresponding encoded meta-definitioninformation 340 of the To side.

A definition point d is set to d=0, and the selected pair of the encodedmeta-definition information 340 is referenced to acquire the maximumvalue D of the definition point d (step S5403). The definition point dis a variable for specifying a sequence number used when the selectedencoded meta-definition information 340 is referenced. For example, inthe case of d=0, the information (the data type ID in this case) isspecified that is set for the sequence number [0] of the encodedmeta-definition information 340 of the From side and the encodedmeta-definition information 340 of the To side.

The maximum value D of the definition point d is the maximum value ofthe sequence number in the selected encoded meta-definition information340. For example, in the case of the pair of the encoded meta-definitioninformation 340 depicted in FIG. 44B, D=4 is set since the maximum valueof the sequence number is “4”.

Reference is made to the information having the definition point d setas the sequence number in the encoded meta-definition information 340 ofthe From side and the encoded meta-definition information 340 of the Toside specified by the current definition point d (step S5404). It isdetermined whether the referenced information has the same values (stepS5405). In the case of the same values (step S5405: YES), the procedureproceeds to step S5411.

On the other hand, if the referenced information does not have the samevalue (step S5405: NO), the sequence number [0] of the encodedmeta-definition information 340 of the From side is referenced toacquire a data type ID and the conversion rule table 4300 is referencedby using the data type ID as a sequence number to acquire the conversionrule tables for data type 4301 to 4304 (step S5406). The acquired tablesare referred to and stored as “conversion rule tables for specified datatype”. The procedure proceeds to step S5407.

For example, although the data type IDs set for the sequence number [0]are different (1 (Char) and 4 (Integer)) in the case of a pair of theencoded meta-definition information 340 depicted in (D) of FIG. 44, thedata type ID: 1 (Char) is acquired which is set for the sequence number[0] of the encoded meta-definition information 340 related toTELEPHONE_NUMBER of the TABLE_A on the From side. This value (data typeID: 1) is used as the sequence number to reference the conversion ruletable 4300 to acquire the conversion rule table for Char type 4301 andthe conversion rule table for specified data type.

At step S5407, a necessary conversion rule (the type conversion ruletable 331 and the cleansing rule table 332) is acquired by using thedefinition point d as the sequence number to make a reference to theconversion rule table for specified data type, and the convertingfunction to be used is acquired by referring to From/To of theconversion rule according to the values of the encoded meta-definitioninformation 340 of the From side and the To side acquired at step S5404(step S5407).

Specifically, in the case of the encoded meta-definition information 340depicted in FIG. 44D, the conversion rule table for the Char type 4301is referenced according to the definition point d=0 to acquire the datatype conversion rule table 331 (see FIG. 36), and a reference is madeaccording to the data type ID: 1 (Char) as the From side and the datatype ID: 4 as the To side to acquire the converting function“character-to-integer conversion”. By giving the same structure to thedata type conversion rule table 331 and the cleansing rule table asdescribed, the acquisition of the converting function is realizedwithout differentiation in the data converting process.

It is determined whether the acquired converting function is effective(step S5408). A criterion may be set in advance for determining whethereffective or ineffective such as “operable when installed”. Ifineffective (step S5408: NO), the data converting process is a failureand therefore, the process is terminated. On the other hand, ifeffective (step S5408: YES), the converting process is executed by theacquired converting function (step S5409). Specifically, for example,the From value is converted and set as the To value. The processeddefinition contents are reflected on the From definition (see FIGS. 23and 45 to 49).

It is then determined whether the converting process by the convertingfunction is successful (step S5410). If not successful (step S5410: NO),the data converting process is a failure and therefore, the process isterminated. On the other hand, if successful (step S5410: YES), theprocedure proceeds to step S5411.

At step S5411, the definition point d is incremented (step S5411). It isthen determined whether d>D is satisfied (step S5412). If d>D is notsatisfied (step S5412: NO), the procedure returns to step S5404 toprocess the next definition point d. On the other hand, if d>D issatisfied (step S5412: YES), since the process is to be completed forall the definition points, the procedure returns to step S5401. At stepS5401, if an unselected pair of the encoded meta-definition information340 does not exist (step S5401: NO), the data converting process (stepS5002) is completed and a shift is made to step S5003 of FIG. 50.

According to the first embodiment, the data type, the data attribute,and the cleansing function may be expanded depending on purpose. Sincethe consistency is ensured when multiple data types, type attributes,and cleansing functions are used, consistency at the time of expansionis not impaired. Therefore, a reduction of the burden on developer isachieved.

The data types, the type attributes, the type attribute values, and thedata type conversion functions, and the cleansing functions may beconstrained to the requisite minimum to achieve a reduction indevelopment costs and to facilitate management. By selectively using thecleansing functions in an efficient manner, the data conversionperformance can be improved. By encoding the data types, the typeattributes, and the type attribute values in the entire system, the dataconversion performance may further be improved.

In the second embodiment, the following functions F1 to F7 are added tothe first embodiment.

F1: A constraint (prerequisite) is set for an existing type attribute toenable the definition of a cleansing function operating within a rangeof the constraint.

F2: When a cleansing process is executed, a main process is executedafter a converting process for keeping the constraint is executed inadvance.

F3: A newly added function performs conversion of another type attributeby itself.

F4: The cleansing process for matching the type attribute is processedin a backward order (from more specialized type attributes).

F5: Expansion is performed such that all type attributes other than thesubject may be handled as the constraint (prerequisite) of the cleansingprocess. Additionally, the converting process is repeatedly executed toprocess the type attributes in the order from the type attribute handledby the conversion executed last until coming full circle.

F6: The order of the process of the function F5 may not necessarily befrom the rear side (more expansive type attributes) toward the frontside (reverse order) and may be executed in normal order (sequentiallyprocessing more basic type attributes toward more expansive typeattributes). Therefore, an efficient process direction may be selected.

F7: The functions F1 to F6 can be selected in a common processingsystem.

Combination patterns (hereinafter, “control pattern P#”) of thefunctions F1 to F6 include the following control patterns P1 to P6.

P1: A constraint (prerequisite) is defined for the cleansing process toimplement the process that keeps the prerequisite. However, theconstraint condition is located before the subject (a more basic typeattribute) (reverse order). This is implemented by a combination of thefunctions F1, F2, and F4.

P2: The cleansing function is given a conversion function for anothertype attribute. However, the type attribute to be converted is locatedbefore the subject (a more basic type attribute) (reverse order). Thisis implemented by a combination of the functions F3 and F4.

P3: A constraint (prerequisite) is defined for the cleansing process toimplement the process that keeps the prerequisite. The type attributeused as the constraint condition may be any type attribute (reverseorder). This is implemented by a combination of the functions F1, F2,and F5.

P4: The cleansing function is given a conversion function for anothertype attribute. The type attribute to be converted may be any typeattribute (reverse order). This is implemented by a combination of thefunctions F3 and F5.

P5: A constraint (prerequisite) is defined for the cleansing process toimplement the process that keeps the prerequisite. The type attributeused as the constraint condition may be any type attribute (forwardorder). This is implemented by a combination of the functions F1, F2,and F6.

P6: The cleansing function is given a conversion function for anothertype attribute. The type attribute to be converted may be any typeattribute (forward order). This is implemented by a combination of thefunctions F3 and F6. Functions F1 to F7 are each described.

FIG. 55 is a diagram of an example of the cleansing specificationdefinition file 301 having a constraint set by the function F1. Thefunction F1 sets a constraint (prerequisite) for an existing typeattribute operates within the range of thereof. The cleansingspecification definition file 301 depicted in FIG. 55 is an example ofadding the function F1 to the cleansing specification definition file301 depicted in FIG. 25 with attention to the personal name type. Thisdepicts an example of newly adding a data type definition description5501 of a personal name to the cleansing specification definition file301 already defined as the Char type.

In FIG. 55, in the data type definition description 5501 of a personalname, a first/second-name spacing process function is defined as a newlyadded cleansing function. In the first/second-name spacing processfunction (in the first embodiment) depicted in FIG. 49, thefirst/second-name spacing process is required to handle all thespecifiable combinations of the type attributes (max_length,char_excode, and char_code) different from the type attribute(name_space) handled by the function itself as the From value(conversion source) and the To value (conversion destination). Forexample, a function is required that executes the first/second-namespacing process handling all the character code systems (SJIS, JEF, andUTF8) as the From value and the To value.

The function F1 is a function that declares an operable condition of thecleansing function for the type attributes (max_length, char_excode, andchar_code) different from the type attribute (name_space) handled by thefunction itself. This function enables the operable condition of thefirst/second-name spacing process function to be specified and thefirst/second-name spacing process function may be simplified.

More specifically, for example, by setting a constraint of“rule=“char_code=SJIS”” in the cleansing rule tag of the data typedefinition description 5501 of a personal name, the first/second-namespacing process function may simply be implemented to operate under thecondition of the type attribute char_code=SJIS due to the constraint andmay be simplified since it is not necessary to support other charactercodes and, additionally, the influence of addition of another functionmay effectively be minimized in such a case that UTF16 is added as acharacter code system.

FIG. 56 is a diagram of an example of conversion by the function F2. Inthe function F2, when a cleansing process is executed, the cleansingprocessing unit executes a main cleansing process after a convertingprocess for keeping the constraint specified by the function F1 isexecuted in advance. In FIG. 55, in the data type definition descriptionof a personal name, the first/second-name spacing process function isdefined as a newly added cleansing function and a constraint of“rule=“char_code=SJIS”” is defined. In FIG. 56, by performing thecharacter code system conversion for keeping the constraint of“char_code=SJIS” before the first/second-name spacing process isexecuted by the newly added first/second-name spacing process function,the first/second-name spacing process may be controlled such that theoperation on the basis of the character code system “SJIS” issufficient.

In the function F3, a newly added function has a function of performingnecessary conversion of a type attribute other than the type attributehandled by the function and allows itself to change the type attribute.Since the definition of constraint of the function F1 and the functionof the cleansing process for keeping the constraint of function F2 arenot necessary in this case, the cleansing specification definition file301 may be the same as the definition of the personal type. The functionof converting another type attribute by the function F3 may be executedby the cleansing control unit on the request from the cleansing functionto be added. When the function F3 is applied to the first/second-namespacing process, a function is provided that performs conversion for thetype attribute char_code=SJIS by itself to change the type attributevalue before the first/second-name spacing process.

The function F4 executes the cleansing process for matching the typeattribute in the backward order (from more specialized type attributes).This is a function of executing the process in reverse order. In thiscase, the type attribute specifiable in the constraint in the functionF1 or the type attribute changed by the function F3 is a type attributelocated before the subject (more basic than the subject).

As a result, since a newly added type attribute (function) is executedin advance and the processed basic type attributes are changed at thesame time, an existing function may be constrained from operating. Thecontrolled return for preprocessing due to the constraint of thefunction F2 (forcible return to a changed portion for reprocessing)becomes unnecessary. Since a type attribute before the subject (morebasic than the subject) is often used as a constraint as in the case ofthe constraint of the character code system in the first/second-namespacing process, the function F4 is useful.

The functions F5 to F7 are functions for handling all the type attributeas constraints. The function F4 limits the constraint (prerequisite) ofthe cleansing process to a (more basic) type attribute defined beforethe type attribute handled by the subject. Since this generally leads tohigher process efficiency, the function F4 should be used forimplementation in the case that this condition is sufficient. On theother hand, the function F5 may be used for implementation in the casethat a (more expansive) type attribute defined after the type attributehandled by the subject must be used as a constraint condition.

FIG. 57 is a diagram of an example of conversion by the function F5. Inthe function F5, expansion is performed such that all the typeattributes other than the subject may be handled as the constraint(prerequisite) of the cleansing process. Additionally, the convertingprocess is repeatedly executed to process the type attributes in theorder from the type attribute handled by the conversion executed lastuntil coming full circle.

FIG. 58 is a diagram of an example of the function F6. The order ofprocess of the Function F5 may not necessarily be from the rear side(more expansive type attributes) toward the front side (reverse order).Therefore, as in the function F6, the process is completed in normalorder (sequentially processing more basic type attributes toward moreexpansive type attributes). Therefore, an efficient process directionmay be selected.

One example of the second embodiment will hereinafter be described. Thedescription will be made with an example of the first/second-namespacing process defined in the personal name data type definitiondescription in the cleansing specification definition file 301 depictedin FIG. 55.

FIG. 59 is an exemplary diagram of an example of introduction of aconstraint. In FIG. 59, a constraint of “char_code=SJIS” is declared inthe first/second-name spacing process defined in the personal name datatype definition description. As a result, the first/second-name spacingprocess is executed when the subject type attribute: name_space (typeattribute ID=4) is different between the From side and the To side andis also executed on the basis that the type attribute value of the typeattribute: char_code (type attribute ID=1) is SJIS (type attributeID=0). Therefore, if additional implementation is desired, it is onlynecessary to declare a constraint in the cleansing rule and since it isnot necessary to support the character code systems other than SJIS, theimplementation of the cleansing function may considerably be simplified.

If a constraint is introduced, a constraint condition table is generatedand deployed as a constraint such that the constraint condition may bereferenced from the cleansing rule as well as the conversion rule at thetime of initialization of the cleansing specification definition file301 (FIG. 51). Specifically, an encoded constraint is set as aconstraint condition table having a structure that may be referencetogether with the cleansing rule table 332 of the cleansing process withthe constraint declared at the same location as a combination of From/Towith the corresponding cleansing function set.

FIG. 60 is a diagram of an example of the constraint condition table. Inthe cleansing rule table 332 for the name_space type attribute handledby the first/second-name spacing process, the first/second-name spacingprocess function is called if From/To indicates (1,0) and (0,1).Therefore, for the constraint condition for the first/second-namespacing process, the constraint condition table for name_space 6000depicted in FIG. 60 is created by similarly setting the encodedconstraint condition “1 (char_code)=0 (SJIS)” at the positions havingFrom/To of (1,0) and (0,1) in the same structure as the cleansing ruletable 332.

FIG. 61 is a diagram of the conversion rule set 330 when the constraintis added. The conversion rule set 330 of FIG. 61 depicts a state ofdeploying the constraint condition onto the conversion rule set 330depicted in FIG. 43. In FIG. 61, a record for the constraint conditionis added to the conversion rule tables for data type 4301 to 4304. Inthe record for the constraint condition, default is indicated by “null”.If the constraint is introduced as depicted in FIG. 59, a pointer to theconstraint condition table is set to a corresponding cleansing rule inthe record for the constraint condition of the corresponding conversionrule tables for data type 4301 to 4304.

In FIG. 61, the calling pointer for the constraint condition table forname_space is set along with the calling pointer for the cleansing rulefor name_space table 332 at the sequence number [4] of the conversionrule table for personal name type. Therefore, if the sequence number [4]of the conversion rule table for personal name type is specified, thecleansing rule table for name_space 332 is called and the constraintcondition table for name_space also becomes referable. An example of thedata converting process in the case of introducing a constraint will bedescribed. An example of the data converting process using a controlpattern P1 combining the functions F1, F2, and F4 will be described.

FIGS. 62 to 66 are explanatory diagrams of a second data conversionexample using the encoded meta-definition information 340 related to theFULL_NAME in the TABLE_A and the TABLE_B depicted in FIG. 44. Theencoding of the data types, the type attributes, and the type attributevalues is performed in advance through the initializing process and themeanings of the codes are recognized in the processes. The cleansingcontrol unit 351 is given the encoded meta-definition information 340depicted in FIG. 62 and the information of values to start theconverting process.

The cleansing control unit compares the data types between the From sideand the To side. Specifically, the values of the sequence number [0](data type) is compared between the encoded meta-definition information340 of the From side and the encoded meta-definition information 340 ofthe To side. In this case, both values are “2” (personal name) andrecognized as the same data type.

Since the data types are the same, the type attributes are then comparedbetween the From side and the To side. Since the function F4 is employedin this example, a comparison is made between the values of the sequencenumber [4] (name_space), which is the type attribute at the end. Sincethe values are “0” (Yes) on the From side and “1” (No) on the To side inFIG. 62, the converting process is specified according to the conversionrule set 330 of FIG. 61.

Specifically, the conversion rule table 4300 is referenced by using thedata type ID: 2 as the sequence number because of the data type ID: 2(personal name) to acquire the conversion rule table for personal nametype 4302.

A reference is then made to the cleansing rule table for name_space 332(FIG. 39) of the sequence number [4] currently compared in theconversion rule table for personal name type 4302. A calling pointer forthe first/second-name spacing process is specified by referring to thecleansing rule table for name_space 332 of FIG. 39 according to “1” (No)on the From side and the “0” (Yes) on the To side, i.e., the values ofthe encoded meta-definition 340 of interest. The first/second-namespacing process is executed after the following process for constraintcondition is executed.

If reference is then made to the constraint condition of the sequencenumber [4] currently compared in the conversion rule table for personalname type 4302, since the constraint condition table for name_space(FIG. 60) is set, a shift is made to a process for the constraintcondition using the constraint condition table for name_space. Aconstraint condition “1 (char_code)=0 (SJIS)” is specified by referringto the constraint condition table for name_space 6000 of FIG. 60according to “1” (No) on the From side and the “0” (Yes) on the To side,i.e., the values of the encoded meta-definition 340 of interest.

As depicted in FIG. 63, to comply with the specified constraintcondition “1 (char_code)=0 (SJIS)”, the process of converting the typeattribute ID: 1 (character code system) from the value of the From sideinto the constraint condition is executed in advance before thefirst/second-name spacing process, based on the name_space typeattribute. FIGS. 63 to 66 depict the states after the execution of theprocesses and the shaded portions indicate the updates of the values.

Specifically, a comparison is made for the type attribute ID: 1specified by the constraint condition “1 (char_code)=0 (SJIS)” betweenthe value of the From definition and the value of the constraintcondition to check whether the constraint condition is satisfied. Inthis example, since the From definition value “1” (JEF)≠the constraintcondition value “0” (SJIS) as depicted in FIG. 62, a process of matchingthe From side with the constraint condition is necessary in advance.Since the From definition is the data type ID: 2, the conversion ruletable 4300 of FIG. 61 is referenced by using the data type ID: 2 as thesequence number to refer to the conversion rule table for personal nametype 4302.

Reference is then made to the cleansing rule table for char_code 332(FIG. 37) of the sequence number [1] currently compared in theconversion rule table for personal name type 4302. Since the From sideis “1” (JEF) and the To side (constraint condition) is “0” (SJIS) asdepicted in FIG. 62, the cleansing rule table for char_code 332 of FIG.37 is referenced by From [1] and To [0] to specify the calling pointerto the character code system converting process. The character codesystem converting process is called by the specified calling pointer toexecute the character code system converting process. As a result, asdepicted in FIG. 63, the object character string “YAMADA KAZUO” of theFrom value having the character code system of JEF is converted intoSJIS, i.e., the constraint condition, and the value of the item number[1] (char_code) of the From definition is updated with “0” (SJIS).

As depicted in FIG. 64, the suspended first/second-name spacing processis then executed. In the first/second-name spacing process, since thesequence number [4] (name_space) of the encoded meta-definitioninformation 340 on the From side indicates “0” (Yes) and the sequencenumber [4] of the encoded meta-definition information 340 on the To sideindicates “1” (No) as depicted in FIG. 63, the object character string“YAMADA KAZUO” converted into SJIS is used as the From value and a apacebetween the first and second names is deleted to set “YAMADAKAZUO” inSJIS as the To value as depicted in FIG. 64. The value of the sequencenumber [4] of the encoded meta-definition information 340 on the Fromside is updated from “0” (Yes) to “1” (No).

As depicted in FIG. 65, the process of the preceding sequence number [3](max_length) is then executed. Specifically, the values of the sequencenumber [3] (max_length) depicted in FIG. 64 are compared between theFrom definition and the To definition. In this case, the values are “20”on the From side and “14” on the To side and since the values aredifferent, a converting process is specified according to the conversionrule set 330 in FIG. 61.

More specifically, the conversion rule table 4300 is referenced by usingthe data type ID: 2 as the sequence number because of the data type ID:2 (personal name) to acquire the conversion rule table for personal nametype 4302.

Reference is then made to the cleansing rule table for max_length 332(FIG. 41) according to the conversion rule of the sequence number [3]currently compared in the acquired conversion rule table for personalname type 4302. Since the max_length type attribute may have anarbitrary value, the calling pointer for the length adjusting process atFrom [0] and To [0] is specified regardless of values of From/To in thecleansing rule table for max_length 332 in FIG. 41.

Since the calling pointer of the constraint condition table is not setat the sequence number [3] in FIG. 61 and is defined as NULL, the lengthadjusting process is directly executed. As depicted in FIG. 65, sincethe From value character string “YAMADAKAZUO” in SJIS with a spacebetween the first and second names deleted has only four characters,i.e., eight bytes, the To value is the same value as the From value evenif the length adjusting process is executed. The value of the Fromdefinition [3] (max_length) is updated with “14” (14 bytes), i.e., thestate after the conversion.

As depicted in FIG. 66, the process of the preceding sequence number [2](char_excode) is then executed. Specifically, the values of the sequencenumber [2] (char_excode) depicted in FIG. 65 are compared between theFrom definition and the To definition. In this case, the values are “0”(external character code 1) in the From definition and “1” (externalcharacter code 2) in the To definition and since the values aredifferent, a converting process is specified according to the conversionrule set 330 in FIG. 61.

More specifically, since the data type ID is 2 (personal name), theconversion rule table 4300 is referenced by using the data type ID: 2 asthe sequence number to acquire the conversion rule table for personalname type 4302.

Reference is then made to the cleansing rule table for char_excode 332(FIG. 38) of the sequence number [2] currently compared in the acquiredconversion rule table for personal name type 4302. Since the From sideis “0” (external character code 1) and the To side (constraintcondition) is “1” (external character code 2) as depicted in FIG. 65,the cleansing rule table for char_excode 332 of FIG. 38 is referenced byFrom [0] and To [1] to specify the calling pointer to the character codesystem converting process.

The character code system converting process is called by the specifiedcalling pointer to execute the character code system converting process.Although the character code system converting process processes are notonly char_excode but also char_code, only char_excode is converted sincethe process has been executed for char_excode because of the constraintcondition. As depicted in FIG. 66, “YAMADAKAZUO” in SJIS and theexternal character code 2 is set as the To value and the value of [2] ofthe From definition is updated with “1” (external character code 2) asthe conversion result.

Since the data type and all the type attributes are consistent, theconverting process is terminated. After the data type at the head, thevalues of definition are sequentially compared from the right and theprocess is specified and executed in the case of a different value. Ifthe constraint condition is set, conversion for keeping the constraintcondition is repeatedly performed in advance. This enables a dataconverting process complying with the constraint to be implemented at aminimum cost without impairing flexibility.

Since the type attributes are sequentially processed from the rear side(right side), a newly added type attribute is evaluated earlier and anew converting function is preferentially executed. For an oldconverting function conflicting with the new converting function, thenew converting function may change the type attribute of the oldconverting function. Therefore, operation may be suppressed under thecontrol of the new converting function.

For example, as depicted in FIG. 66, since the type attributes aresequentially processed from the rear side (right side), the newly addedtype attribute char_excode is evaluated earlier than the old typeattribute char_code and the new converting function (character codesystem converting process) is preferentially executed. Since both thenew converting function and the old converting function execute thecharacter code system converting process in this case, the charactercode system converting process of the old converting function may besuppressed by converting the char_code type attribute by the charactercode system converting process executed first and a redundant processmay be prevented.

The data converting process procedure of the data converting apparatus300 according to the second embodiment will be described with referenceto FIGS. 67 to 72.

FIG. 67 is a flowchart of the data converting process procedure of thedata converting apparatus 300 according to the second embodiment. First,the initializing unit 311 executes the initializing process (stepS6701). Details of the initializing process (step S6701) will bedescribed with reference to FIGS. 68 and 69.

The cleansing processing unit 312 executes the data converting process(step S6702). Details of the data converting process (step S6702) willbe described with reference to FIG. 71. It is then determined whetherthe data conversion is to be continued (step S6703). The criterion maybe operational input from a user or the presence of data to beconverted.

If continued (step S6703: YES), the procedure proceeds to step S6702 toexecute the data converting process. On the other hand, if not continued(step S6703: NO), a release process is executed (step S6704). In therelease process, a resource on the memory obtained at the initializingprocess (step S6701) is released. This leads to termination of the dataconverting process.

FIG. 68 is a flowchart of a process procedure (first half) of theinitializing process (step S6701) executed by the initializing unit 311depicted in FIG. 67. As depicted in FIG. 68, the cleansing specificationdefinition file 301 is read and analyzed (step S6801). A control-patternselecting process is then executed (step S6802). In the control-patternselecting process (step S6802), a corresponding control pattern isselected from the control patterns P1 to P6 and the control pattern P0corresponding to the first embodiment. The details of thecontrol-pattern selecting process (step S6802) will be described laterwith reference to FIG. 70.

If a control pattern P is selected by the control-pattern selectingprocess (step S6802), a data type code table creating process isexecuted (step S6803). Specifically, data type IDs are added to the datatypes. For example, as depicted in FIG. 26, entirely unique integersstarting from one are added as the data type IDs consecutively without askip in the order of definition.

A type attribute code table creating process is executed (step S6804).Specifically, type attribute IDs are added to the type attributes. Forexample, as depicted in FIGS. 27 to 29, integers unique within a datatype starting from one consecutively without a skip in the order ofdefinition are added as the type attribute IDs to all the typeattributes in the order from the data type of the ancestor. Between thedata types having the inheritance relationship, the type attribute IDsof common type attributes are controlled to be consistent in the entiresystem.

A type attribute value code table creating process is executed (stepS6805). Specifically, as depicted in FIGS. 30 to 35, type attributevalue IDs are added to the type attribute values. The details of thetype attribute value code table creating process (step S6805) are thesame as the process contents depicted in FIG. 53 and will not bedescribed.

After the type attribute value code table creating process (step S6805),as depicted in FIG. 36, the data type conversion rule table 331 isgenerated (step S6806). As depicted in FIGS. 37 to 42, the cleansingrule table 332 is generated (step S6807). The procedure proceeds to stepS6901 of FIG. 69.

FIG. 69 is a flowchart of a process procedure (second half) of theinitializing process (step S6701) executed by the initializing unit 311depicted in FIG. 67. After the cleansing rule table 332 is generated, inFIG. 69, the selected control pattern is specified (step S6901). If thecontrol pattern P is P0, P2, P4, or P6 (step S6901: P0, p2, P4, P6), theprocedure proceeds to step S6903. On the other hand, if the controlpattern P is P1, P3, or P5 (step S6901: P1, P3, P5), the constraintcondition table is generated as depicted in FIG. 60 (step S6902). Theprocedure proceeds to step S6903.

At step S6903, as depicted in FIG. 61, the conversion rule set 330 isorganized (step S6903). The meta-definition file 304 is then read andanalyzed (step S6904). The types of analyzed information aresequentially determined (step S6905). Specifically, it is determinedwhether the information is a data type, a type attribute, or a typeattribute value. The determination is made according to the order ofdescription in the meta-definition file 304.

In the case of the data type (step S6905: DATA TYPE), the data type istransformed into ID (step S6906). Specifically, the data type code table321 (FIG. 26) is referenced for the transformation into the data typeID. The procedure proceeds to step S6911.

If the type of the information is a type attribute (step S6905: TYPEATTRIBUTE), the type attribute is transformed into ID (step S6907).Specifically, the type attribute code table 322 (FIGS. 27 to 29) isreferenced for the transformation into the type attribute ID. Theprocedure proceeds to step S6911.

If the type of the information is a type attribute value (step S6905:TYPE ATTRIBUTE VALUE), it is determined whether the type attribute valueis encoded (step S6908). If the type attribute value is encoded (stepS6908: YES), the type attribute value code table 323 (FIGS. 30 to 35) isreferenced for the transformation into the type attribute value ID (stepS6909). The procedure proceeds to step S6911.

If the type attribute value is not encoded (step S6908: NO), an integervalue of the type attribute value is directly defined as the typeattribute value ID (step S6910). The procedure proceeds to step S6911.

At step S6911, as depicted in FIG. 44, the item definition of datamodels in the meta-definition file 304 is encoded to create the itemmeta-definition table (step S6911). Specifically, the sequence number[0] is set for the data type ID and the sequence numbers [1], [2], [3],. . . are set for the type attribute value IDs or the type attributevalues (if not encoded) of the type attribute having the type attributeIDs identical to the sequence numbers. For example, if the itemmeta-identification table having the data model related to the employeeitem of the TABLE_A is created, the sequence number [0] is set for thedata type ID: 4 (see FIG. 26) indicative of the integer type that is thedata type of the EMPLOYEE_NUMBER item and the sequence number [1] is setfor the type attribute value: 12 (see FIG. 35) of the max_digit typeattribute (see FIG. 29) that is the type attribute ID: 1 of the integertype as depicted in FIG. 44. Since the type attribute value of themax_digit type attribute is a type attribute value not encoded, the typeattribute value: 12 specified in the meta-definition file 304 isdirectly used for the setting.

It is then determined whether all the data models in the meta-definitionfile 304 are encoded (step S6912). If not all the data models have beenencoded (step S6912: NO), the procedure returns to step S6905 to encodethe remaining data models. On the other hand, if all the data models areencoded (step S6912: YES), the encoded meta-definition information 340is configured as a group of encoded item meta-definition as depicted inFIG. 44 (step S6913). Subsequently, a shift is made to the dataconverting process (step S6702).

FIG. 70 is a flowchart of a process procedure of the control-patternselecting process (step S6802) depicted in FIG. 68. It is determinedwhether the cleansing specification definition file 301 has a constraint(step S7001). Specifically, for example, it is determined whether aconstraint is declared as described in the personal name data typedefinition description 5501 of FIG. 55.

If a constraint exists (step S7001: YES), the direction of constraint isdetermined (step S7002). The direction of constraint is determined basedon, for example, whether all the type attributes to be restricted arelocated in a higher order than the subject (the type attribute havingthe cleansing definition with the constraint declared), whether all thetype attributes to be restricted are located in a lower order than thesubject, and whether the type attributes to be restricted are a mixtureof the type attributes in lower and higher orders than the subject.

For example, since the constraint is “rule=“char_code=SJIS”” in theexample of FIG. 55, the type attribute to be restricted is “char_code”.The subject (type attribute) is the type attribute “name_space” havingthe cleansing rule (<CL_RULE> tag) with the constraint“rule=“char_code=SJIS”” declared. In this case, since “char_code” isdefined higher than “name_space” (described in an upper line in the samedata type definition or in the data type definition of the Supertype) inFIG. 55, the direction of constraint is the “higher order”.

In the case of a higher order (step S7002: HIGHER ORDER), the controlpattern P1 is selected (step S7003) and the procedure proceeds to stepS6803. On the other hand, in the case of a lower order or mixture (stepS7002: LOWER ORDER or MIXTURE), it is determined whether conflictingconverting functions are present (step S7004). Conflicting convertingfunctions will be described.

For example, when a character code system converting function (referredto as a character code system converting function 2) capable ofconverting a difference in external characters (capable of supportingthe char_excode type attribute as well as the char_code type attribute)is added to an environment using a general character code systemconverting function (referred to as a character code system convertingfunction 1) that performs character code system conversion for thechar_code type attribute, it is desirable to use the efficient charactercode system converting function 1 for the conversion of data having thesame external character systems and to use the highly-functionalcharacter code system converting function 2 for the conversion of datahaving different external character systems.

When converting functions having a converting function for the same typeattribute value are allowed to be used at the same time, both arereferred to as “conflicting converting functions”. Since ahighly-functional cleansing function such as the character code systemconverting function 2 is generally set as conversion for type attributeson the rear side, the conflict may be resolved by using a controlpattern that first processes the type attributes on the rear side torealize efficient selective usage.

If conflicting converting functions are present (step S7004: YES), thecontrol pattern P3 is selected (step S7005) and if no conflictingconverting function is present (step S7004: NO), the control pattern P5is selected (step S7006). The procedure proceeds to step S6803.

On the other hand, if the cleansing specification definition file 301has no constraint at step S7001 (step S7001: NO), it is determinedwhether a converting function is present that has the function F3applying a constraint by itself (step S7007). Specifically, as describedin <Function F3>, since no constraint is defined in the cleansingspecification definition file 301, for example, information indicativeof the presence of the function applying a constraint and the specifictype attribute to be restricted is described in a portion for definingthe cleansing function in the cleansing specification definition file inadvance, and the “presence of the function applying a constraint” isdetermined based on the information. The “specific type attribute to berestricted” is information necessary for the determination at step S7011described later.

If no converting process applying a constraint is present (step S7007:NO), it is determined whether conflicting converting functions arepresent (step S7008). The process at step S7008 is the same process asthat at step S7004. If conflicting converting functions are present(step S7008: YES), the control pattern P2 is selected (step S7009). Onthe other hand, if no conflicting converting function is present (stepS7008: NO), the control pattern P0 is selected (step S7010). Theprocedure proceeds to step S6803.

If no converting process applying a constraint is present (step S7007:NO), the direction of constraint is determined (step S7011). Althoughthe process at step S7011 is the same process as that at step S7002, thetype attribute to be restricted requires a unit of separately acquiringinformation as described at step S7007. In the case of the lower order(step S7011: LOWER ORDER), the control pattern P0 is selected (stepS7012).

In the case of the higher order (step S7011: HIGHER ORDER), the controlpattern P2 is selected (step S7013). In the case of the mixture (stepS7011: MIXTURE), it is determined whether conflicting convertingfunctions are present (step S7014). The process at step S7014 is thesame process as that at step S7004. If the conflicting convertingfunctions are present (step S7014: YES), the control pattern P4 isselected (step S7015). On the other hand, if no conflicting convertingfunction are present (step S7014: NO), the control pattern P6 isselected (step S7016). The procedure proceeds to step S6803.

FIG. 71 is a flowchart of a process procedure of the data convertingprocess (step S6702) depicted in FIG. 67. It is determined whether anunselected pair of the encoded meta-definition information 340 ispresent (step S7101). If no unselected pair of the encodedmeta-definition information 340 is present (step S7101: NO), theprocedure proceeds to step S6703. On the other hand, if an unselectedpair of the encoded meta-definition information 340 is present (stepS7101: YES), the unselected pair of the encoded meta-definitioninformation 340 is selected (step S7102).

The control pattern P is specified (step S7103). If the control patternP is P0 to P2 (step S7103: P0 to P2), the procedure proceeds to stepS7105. On the other hand, if the control pattern P is P3 to P6 (stepS7103: P3 to P6), the control point R is set to R=0 (step S7104) and theprocedure proceeds to step S7105.

At step S7105, the definition point d is set to d=0, and the selectedpair of the encoded meta-definition information 340 is referenced toacquire the maximum value D of the definition point d (step S7105).

The control pattern P is then specified (step S7106). If the controlpattern P is P0, P5, or P6 (step S7106: P0, P5, P6), the procedureproceeds to step S7108. On the other hand, if the control pattern P isP1 to P4 (step S7106: P1 to P4), the definition point d is set to themaximum value D (step S7107) and the procedure proceeds to step S7108.Reference is made to the information having the current definition pointd set as the sequence number in the specified encoded meta-definitioninformation 340 of the From side and the encoded meta-definitioninformation 340 of the To side (step S7108). It is determined whetherthe referenced information has the same values (step S7109).

In the case of the same values (step S7109: YES), the control pattern Pis specified (step S7110). If the control pattern P is P1 to P4 (stepS7110: P1 to P4), the definition point d is decremented (step S7111) andthe procedure proceeds to step S7113. On the other hand, if the controlpattern P is P0, P5, or P6 (step S7110: P0, P5, P6), the definitionpoint d is incremented (step S7112) and the procedure proceeds to stepS7113.

At step S7113, the control pattern P is specified again (step S7113). Ifthe control pattern P is P1 or P2 (step S7113: P1, P2), it is determinedwhether the definition point d is d=0 (step S7114). If d=0 is notsatisfied (step S7114: NO), the procedure returns to step S7108 and ifd=0 is satisfied (step S7114: YES), the procedure returns to step S7101.

If the control pattern P is P0 (step S7113: P0), it is determinedwhether the definition point d is d=D (step S7115). If d=D is notsatisfied (step S7115: NO), the procedure returns to step S7108 and ifd=D is satisfied (step S7115: YES), the procedure returns to step S7101.

If the control pattern P is P3 to P6 (step S7113: P3 to P6), it isdetermined whether the definition point d is d=R (step S7116). If d=R isnot satisfied (step S7116: NO), the procedure returns to step S7108 andif d=R is satisfied (step S7116: YES), the procedure returns to stepS7101.

At step S7109, if the information referenced at S7108 does not have thesame values (step S7109: NO), the procedure proceeds to step S7201 ofFIG. 72.

FIG. 72 is another flowchart of the data converting process (step S6702)depicted in FIG. 67.

The encoded meta-definition information 340 of the From side isreferenced according to the sequence number [0] to acquire a data typeID of the From side, and the conversion rule table 4300 is referenced byusing the acquired data type ID as the sequence number to acquire thecorresponding conversion rule tables for data types 4301 to 4304 (stepS7201). The acquired tables are referred to as “conversion rule tablesfor specified data type”.

The control pattern P is then specified (step S7202). If the controlpattern P is P0, P2, P4, or P6 (step S7202: P0, P2, P4, P6), theprocedure proceeds to step S7207. On the other hand, if the controlpattern P is P1, P3, or P5 (step S7202: P1, P3, P5), it is determinedwhether a constraint condition exists (step S7203).

In the process at step S7203, the conversion rule tables for specifieddata type is referenced by using the definition point d as the sequencenumber to acquire the conversion rule table (the data type conversionrule table 331 or the cleansing rule table 332); the conversion ruletable for a constraint condition is referenced by using the values ofthe encoded meta-definition pair referenced at step S7108 as thesequence numbers of From/To; it is determined that no constraintcondition exists in the case of NULL; and it is determined that aconstraint condition exists in the case of other than NULL to store apointer to the constraint condition table.

If the values of the encoded meta-definition pair referenced at stepS7108 are arbitrary values that are not encoded, the conversion ruletable is referenced by setting both of the sequence numbers of From/Toas [0] to refer to a constraint condition. If no constraint condition ispresent (step S7203: NO), the procedure proceeds to step S7207.

On the other hand, if a constraint condition is present (step S7203:YES), the constraint condition is executed (step S7204). The executionof the constraint condition is a process conforming to a normalcleansing process except that a state of the current value is used asthe From definition and the constraint condition as the To definition,as described with reference to FIGS. 62 to 64. The control pattern P isspecified again (step S7205). If the control pattern P is P1 (stepS7205: P1), the procedure proceeds to step S7207. If the control patternP is P3 or P5 (step S7205: P3, P5), a constraint point R is set as thecurrent definition point d (step S7206) and the procedure proceeds tostep S7207.

At step S7207, the conversion rule tables for specified data type isreferenced by using the definition point d as the sequence number toacquire the conversion rule table (the data type conversion rule table331 or the cleansing rule table 332) and a converting function to beexecuted is acquired by using the values of the encoded meta-definitionpair referenced at step S7108 as the sequence numbers of From/To for theconversion rule table (step S7207). If the values of the encodedmeta-definition pair referenced at step S7108 are arbitrary values thatare not encoded, the conversion rule table is referenced by setting bothof the sequence numbers of From/To as [0] to acquire the convertingfunction to be executed (step S7207).

The converting process is executed by the acquired converting function(step S7208). Specifically, for example, the From value is converted andset as the To value. The processed definition contents are reflected onthe From definition (see FIGS. 45 to 49). The procedure returns to stepS7110 of FIG. 71.

In the second embodiment, the cleansing function operating under variousconditions may be developed with less burden as described. The additionof a new cleansing function can be flexibly supported without affectingexisting functions. Even if the cleansing function is executed fromvarious functions including a real-time process, higher performance canbe achieved.

The functional configuration of the data converting apparatus describedin the first and second embodiments will be described.

FIG. 73 is a block diagram of a functional configuration of the dataconverting apparatus according to the embodiments. FIG. 73 depictsfunctional configurations of the initializing unit 311 and the cleansingprocessing unit 312. The functional configuration of the initializingunit 311 will first be described. It is assumed that a storage unit 7310stores the cleansing specification definition file 301, the typeconverting function library 302, the cleansing function library 303, andthe meta-definition file 304.

The initializing unit 311 includes a specification-definitioninformation acquiring unit 7300, a first setting unit 7301, a secondsetting unit 7302, an constructing unit 7303, a third setting unit 7304,a meta-definition information acquiring unit 7305, a generating unit7306, and a compensating unit 7307.

The specification-definition information acquiring unit 7300 has afunction of acquiring specification definition information that definesspecification (such as data types, type attributes, and type attributevalues) of metadata handled by the data converting apparatus usable asthe metadata of the conversion source (From side) and the metadata ofthe conversion destination (To side) and a data converting functionachievable as a combination thereof.

The specification definition information is information that definesspecification of data conversion and may be cleansing specificationdefinition file 301, for example. The metadata is not data to beconverted and includes information related to the property of the datato be converted and relevant information between object data. In thecleansing specification definition file 301, the metadata corresponds todata types, type attributes, and type attribute values representative ofthe property of data, tables, columns, and mapping representative of thestructure of data, etc.

The data converting function is a function of converting a data value ofthe conversion source (From value) having the property defined by themetadata of the conversion source (From definition) into a data value(To value) defined by the metadata of the conversion destination (Todefinition). Specifically, the data converting function corresponds tothe type converting function or the cleansing function depicted in FIGS.3A to 3C. In the cleansing specification definition file 301, in thecase of the type converting function, the definition is achieved withthe DTCV_RULE tag 411 along with a combination of convertible datatypes. In the case of the cleansing function, the definition is achievedwith the cleansing rule definition tag (CL_RULE tag) 414 along with acombination of convertible type attributes and type attribute values.

The first setting unit 7301 has a function of determining thespecification of metadata usable in the data converting apparatus, basedon the specification definition information acquired by thespecification-definition information acquiring unit 7300 andtransforming the metadata specification prescribed in externalexpression into IDs (numeric values) as much as possible to create themetadata specification in internal expression for the determinedspecification of metadata. A metadata code is a numeric codecorresponding to the external expression of the metadata specification.A metadata encoding table is created as an administration table forcorrelating the external expression of the metadata specification withthe metadata code.

For example, as depicted in FIG. 26, if the metadata specification is adata type, the metadata code is a data type ID. The first setting unit7301 sets the data type code table 321 as the metadata encoding table.

As depicted in FIGS. 27 to 29, if the metadata specification is a typeattribute, the metadata code is a type attribute ID. The first settingunit 7301 sets the type attribute code table 322 as the metadataencoding table. As depicted in FIGS. 30 to 33, if the metadataspecification is a type attribute value, the metadata code is a typeattribute value ID. The first setting unit 7301 sets the type attributevalue code table 323 as the metadata encoding table.

If the metadata specification is able to have an arbitrary value, theexternal expression of the metadata specification is directly used asthe metadata code. For example, as depicted in FIG. 34, the typeattribute value of the type attribute: max_length may be an arbitraryvalue, the metadata encoding table is set as the type attribute valuecode table 323 that records information indicative of “directly using avalue”.

If description is defined such that a first metadata specificationdefined by the specification definition information is inherited by asecond metadata specification, the metadata encoding table may be setsuch that the metadata code of the metadata specification in a lowerhierarchy of the first metadata specification in the specificationdefinition information is imported as the metadata specification in alower hierarchy of the second metadata specification.

Specifically, the inheritance of the data type depicted in FIG. 9 may beprescribed. For example, if the first metadata specification is the chartype and the second metadata specification is the personal name type,the type attribute and the type attribute value in the lower hierarchiesof the personal type may inherit the type attribute and the typeattribute value of the char type to set the type attribute code table322 depicted in FIG. 27.

Since the inheriting function unifies the common portion of the metadataspecification in the lower hierarchies, the contradiction in theprocessing system overall is resolved and redundant data conversion canbe prevented.

The second setting unit 7302 has a function of setting the dataconversion rule table by correlating a data converting functionaccording to a combination of a metadata code of the conversion sourceand a metadata code of the conversion destination by reference to themetadata encoding table set by the first setting unit 7301. The dataconversion rule table is a table that specifies a data convertingfunction according to a combination of a metadata code of the conversionsource and a metadata code of the conversion destination. The dataconversion rule table corresponds to the data type conversion rule tableand the cleansing rule table in the embodiments.

For example, if the metadata specification is a data type, the dataconversion rule table is the data type conversion rule table as depictedin FIG. 36 and if the metadata specification is a type attribute, thedata conversion rule table is the cleansing rule table for performingthe data conversion (cleansing) based on the type attribute value asdepicted in FIGS. 37 to 42.

The constructing unit 7303 has a function of constructing a conversionrule by correlating a higher-order conversion rule code with eachconversion rule table set by the second setting unit 7302. Theconversion rule code is a code assigned to a higher-order metadataspecification to which the conversion rule table is applied.

Specifically, for example, if the highest-order metadata specificationis a data type, the highest-order conversion rule code is the data typeID as depicted in FIG. 43. To the highest-order data type conversionrule table, zero is assigned as a conversion rule code in the hierarchylocated immediately below. If the metadata specification is a typeattribute, a type attribute ID is assigned to the cleansing rule table332 applied to each type attribute as depicted in FIG. 43.

The constructing unit 7303 organizes the tables to construct theconversion rule tables for data type 4301 to 4304 as a conversion rule.If multiple data types are present, the conversion rule tables for datatype 4301 to 4304 are organized to construct the conversion rule set 330as depicted in FIG. 43.

The third setting unit 7304 has a function of copying the conversionrule table with the data converting function set to assign a constraintcondition instead of the data converting function to set a constraintcondition table, if the constraint condition is set for the dataconverting function. Specifically, for example, in the secondembodiment, the cleansing table 332 is copied and the constraintcondition corresponding to the data converting function is set to createthe constraint condition table 6000 as described with reference to FIG.60. The constructing unit 7303 configures the constraint condition table6000 to be referable along with the data converting function as depictedin FIG. 61.

The meta-definition information acquiring unit 7305 has a function ofacquiring meta-definition information that defines metadata of theconversion source and the conversion destination. The meta-definitioninformation is information that defines metadata representative of theproperty and structure of the data of the conversion source and theconversion destination and that defines the correlation between theconversion source and the conversion destination. For example, themeta-definition information corresponds to the meta-definition file 304.

The generating unit 7306 has a function of generating encodedmeta-definition information by encoding each of the metadata in themeta-definition information acquired by the meta-definition informationacquiring unit 7305 by using the conversion rule code of the metadataassigned by the first setting unit 7301. Specifically, for example, fora data type, a type attribute, and a type attribute value in themeta-definition file 304, the data type, the type attribute, and thetype attribute value are encoded by a data type ID, a type attribute ID,and a type attribute value ID. This enables efficient checking of theconversion rule set 330 by performing the standardized encoding in thewhole processing system.

The compensating unit 7307 has a function of compensating skippedmetadata by utilizing the default value assignment of the metadataspecification acquired from the specification-definition informationacquiring unit 7300 and stored in the compensating unit, if the skippedmetadata is present in the meta-definition information acquired by themeta-definition information acquiring unit 7305. Specifically, forexample, as depicted in FIG. 16, if “char_code: JEF”, “max_length: 20”,and “name_space: Yes” are assigned as default attribute values of thetype attributes in the cleansing specification definition file 301, whenthe meta-definition information acquiring unit acquires themeta-definition file 304 with the type attributes skipped as depicted inthe lower portion of FIG. 17, the stored type attributes and the defaultvalues are used to compensate and correct the encoded meta-definitioninformation equivalent to the meta-definition file 304 depicted in theupper portion of FIG. 17.

Therefore, simplification may be achieved in the meta-definition file304 while maintaining the definitions. The functional configuration ofthe cleansing processing unit 312 will then be described.

As depicted in FIG. 73, the cleansing processing unit 321 includes aninput unit 7311, a detecting unit 7312, a determining unit 7313, aconverting function specifying unit 7314, a table specifying unit 7315,a converting unit 7316, an updating unit 7317, and an output unit 7318.The detecting unit 7312, the determining unit 7313, the convertingfunction specifying unit 7314, and the table specifying unit 7315 arefunctions making up the cleansing control unit 351 depicted in FIG. 3A.

The input unit 7311 has a function of receiving the input of data to beconverted. Specifically, for example, the input unit 7311 receives thedata to be converted having the metadata of the conversion sourcedefined by the meta-definition file 304. If the metadata of theconversion source of the data to be converted is identified byspecifying the information identifying the metadata of the conversionsource along with the input of the data to be converted, the dataconversion may be executed according to the meta-definition file 304since the conversion destination is defined by the meta-definition file304. The information identifying the metadata of the conversiondestination may be configured to be specified at this point.

The detecting unit 7312 has a function of detecting the metadata codesof the conversion source and the conversion destination having thematching conversion rule code in the conversion source and theconversion destination by reference to the encoded meta-definitioninformation 340. Specifically, for example, as depicted in FIG. 44, thedata type ID/type attribute value ID of the conversion source (TABLE_A)and the data type ID/type attribute value ID of the conversiondestination (TABLE_B) having the matching sequence number correspondingto the conversion rule code are detected in the conversion source(TABLE_A) and the conversion destination (TABLE_B).

For example, in FIG. 44B, for the matching identical sequence number: 0(data type) of the conversion source (FULL_NAME in the TABLE_A) and theconversion destination (FULL_NAME in the TABLE_B), the data type ID: 2(personal name type) of the conversion source (FULL_NAME in the TABLE_A)and the data type ID: 2 (personal name type) of the conversiondestination (FULL_NAME in the TABLE_B) are detected.

If the conversion rule code (sequence number) is assigned as aconsecutive number in order of priority of the metadata as depicted inFIG. 44 in the encoded meta-definition information 340, the metadatacodes (data type ID/type attribute ID) of the conversion source(TABLE_A) and the conversion destination (TABLE_B) may be detected indescending order of priority to determine the matching. As a result,since the cleansing is sequentially executed in the order from a moreimportant type attribute, the occurrence of useless processes can beprevented and the cleansing process can be simplified.

The determining unit 7313 has a function of determining whether themetadata code of the conversion source detected by the detecting unit7312 matches the metadata code of the conversion destination. In thecase of matching, since properties the same as the conversion source isrequired as the conversion destination, it is not necessary to convertthe property prescribed by the metadata code of the conversion sourceinto the property prescribed by the metadata code of the conversiondestination. Therefore, more efficient data conversion can be achievedby detecting the matching of the metadata codes and not delivering themetadata codes to the converting process.

In the case of no matching, the table specifying unit 7315 specifies aconverting rule table. The table specifying unit 7315 has a function ofspecifying a corresponding conversion rule table from the data typeconversion rule table 331 (in the case of the conversion rule code=0) orthe cleansing rule table 332 (in the case of the conversion rule code≠0)by referring to the conversion rule, based on the conversion rule codeof the conversions source, if mismatch is determined by the determiningunit 7313.

In the identification of the conversion rule table, the correspondingconversion rule tables for data type 4301 to 4304 are specified byreferring to the conversion rule set 330 depicted in FIG. 43 and usingthe value of the item number [0] of the encoded meta-definition of theconversion source as the item number to refer to the conversion rule4300, and the conversion rule table (the data type conversion rule table331 or the cleansing rule table 332) is specified by using themismatched conversion rule code (the item number of the encodedmeta-definition) as the item number to refer to the conversion ruletables for data type.

For example, in the case of the conversion rule code: 1 in (B) of FIG.44, the sequence number [1] (char_code) indicates the type attributevalue ID: 1 (JEF) in the conversion source (FULL_NAME in the TABLE_A)and the type attribute value ID: 0 (SJIS) in the conversion destination(FULL_NAME in the TABLE_B) and the type attribute value IDs aremismatched. In this case, the sequence number [0] (data type) of theconversion source (FULL_NAME in the TABLE_A) is used as the sequencenumber to refer to the conversion rule 4300 to specify the conversionrule table for data type 4301 for the Char type, and the conversion rulecode: 1 to be processed is used as the sequence number to refer to thespecified conversion rule table for data type 4301 to specify thecleansing rule table 332 for char_code. If the conversion rule code tobe processed is [1], the conversion rule table for data type 4301 isreferenced by using the sequence number [0] to specify the data typeconversion rule table 331 for the Char type.

The converting function specifying unit 7314 has a function ofspecifying a data converting function according to a combination of themetadata code of the conversion source and the metadata code of theconversion destination by referring to the conversion rule table, basedon the determination result determined by the determining unit 7313.Specifically, for example, the conversion rule table (data typeconversion rule table 331 or the cleansing rule table 332) specified bythe table specifying unit 7315 is referenced by using the metadata codeof the conversion source as the sequence number of the From side and themetadata code of the conversion destination as the sequence number ofthe To side to specify the data converting function corresponding to acombination of the metadata code of the conversion source and themetadata code of the conversion destination.

For example, in the example of the conversion rule code: 1 in (B) ofFIG. 44, the cleansing rule table for char_code 332 (see FIG. 37) isreferenced by using the type attribute value ID: 1 (JEF) of theconversion source (FULL_NAME in the TABLE_A) as the sequence number ofthe From side and the type attribute value ID: 0 (SJIS) of theconversion destination (FULL_NAME in the TABLE_A) as the sequence numberof the To side. As a result, the “character code system convertingfunction” may be specified as the data converting function.

In the conversion rule table (the data type conversion rule table 331 orthe cleansing rule table 332), if the metadata codes of the conversionsource and the conversion destination are the same, the data conversionfunction is not assigned (see FIGS. 36 to 40). If the metadata codes ofthe conversion source and the conversion destination are identical, thedetermining unit 7313 determines that the conversion is unnecessary andthe combination is not used so as not to execute the subsequentconverting process. The control may be performed without relying on thedetermining unit such that the conversion by the converting unit is notperformed, if the data converting function is not assigned to theconversion rule table. Therefore, useless data conversion can beprevented.

The converting unit 7316 has a function of converting the object data ofthe conversion source having the property prescribed by the metadata ofthe conversion source into the property prescribed by the metadata ofthe conversion destination by using the data converting functionspecified by the converting function specifying unit 7314. Specifically,for example, the data to be converted is converted by giving themetadata of the conversion source, the metadata of the conversiondestination, and the data to be converted together to the dataconverting function.

For example, in the example of the conversion rule code: 1 in (B) ofFIG. 44, the data to be converted expressed in JEF is converted intodata expressed in SJIS by giving the type attribute value: 1 (JEF) ofthe conversion source, the type attribute value: 0 (SJIS) of theconversion destination, and the data to be converted (e.g., a characterstring) to the character code system converting function.

The updating unit 7317 has a function of updating the metadata code ofthe conversion source converted by the converting unit 7316 into themetadata code of the conversion destination in the encodedmeta-definition information 340 before the next execution of thedetecting process by the detecting unit 7312, if the converting unit7316 performs conversion. Specifically, for example, in comparison ofthe type attribute value ID at the sequence number [1] (char_code) ofthe conversion source (FULL_NAME in the TABLE_A) between FIGS. 45 and46, the type attribute value ID: 1 (JEF) of FIG. 45, i.e., before theconversion is update in FIG. 46, i.e., after the conversion, with thetype attribute value ID: 0 (SJIS) at the sequence number [1] of theconversion destination (FULL_NAME in the TABLE_B) of FIG. 45, i.e.,before the conversion (Char_excode is converted at the same time by theconverting function in FIGS. 45 and 46).

As a result, the past conversion is subsequently reflected and both theconversion source (FULL_NAME in the TABLE_A) and the conversiondestination (FULL_NAME in the TABLE_B) have the type attribute value ofSJIS, which eliminates the need for the data conversion. Therefore, thedata to be converted (the conversion source) is processed by the encodedmeta-definition information 340 in the latest state and the efficientdata conversion may be achieved.

As depicted in the second embodiment, if the constraint condition table6000 exists, the data conversion is performed for the conversion rulecode specified by the constraint condition according to the constraintcondition before the data converting function corresponding to theconversion rule code with the constraint condition set. Therefore, sincethe data converting function with the constraint condition set can beimplemented to operate based only on the constraint condition and doesnot have to support other metadata, the implementation can beconsiderably simplified.

The output unit 7318 has a function of outputting the data after theconversion. Specifically, for example, the data is transmitted to acomputer that is the conversion destination or is stored to the storageunit 7310. The data may be displayed on a display or printed by aprinter.

The first and second embodiments effect improved usability and reducedeveloper burden along with the higher process efficiency.

The data converting method described in the present embodiments may beimplemented by executing a prepared program on a computer such as apersonal computer and a workstation. The program is stored on anon-transitory, computer-readable recording medium such as a hard disk,a flexible disk, a CD-ROM, an MO, and a DVD, read out from the recordingmedium, and executed by the computer. The program may be a transmissionmedium that can be distributed through a network such as the Internet.

All examples and conditional language recited herein are intended forpedagogical purposes to aid the reader in understanding the inventionand the concepts contributed by the inventor to furthering the art, andare to be construed as being without limitation to such specificallyrecited examples and conditions, nor does the organization of suchexamples in the specification relate to a showing of the superiority andinferiority of the invention. Although the embodiments of the presentinvention have been described in detail, it should be understood thatthe various changes, substitutions, and alterations could be made heretowithout departing from the spirit and scope of the invention.

1. A data converting apparatus comprising: a storage unit that storesencoded meta-definition information that assigns a metadata code as aunique code to an element making up metadata in meta-definitioninformation that defines metadata indicative of a property related todata of a conversion source and a conversion destination, a dataconverting function that converts conversion source data having aproperty prescribed by the metadata for the conversion source intoconversion destination data having a property prescribed by the metadatafor the conversion destination, a conversion rule table that assigns thedata converting function according to a combination of a metadata codefor the conversion source and a metadata code the conversiondestination, and a conversion rule that correlates with each of theconversion rule tables, a relevant metadata code as a conversion rulecode; an input unit that receives input of data to be converted; adetecting unit that refers to the encoded meta-definition informationstored in the storage unit and detects the metadata codes for theconversion source and the conversion destination for which theconversion rule code matches between the conversion source and theconversion destination; a determining unit that determines whether thedetected metadata codes for the conversion source and for the conversiondestination match; a converting function specifying unit that, byreferring to a conversion rule stored in the storage unit and based onthe determination result obtained by the determining unit, specifies thedata converting function, according to the combination of the metadatacode for the conversion source and the metadata code for the conversiondestination; and a converting unit that, by using the data convertingfunction specified by the converting function specifying unit, convertsthe conversion source data, which is the data to be converted, to have aproperty prescribed by metadata for the conversion destination.
 2. Thedata converting apparatus according to claim 1, wherein if matching ofthe metadata codes is determined by the determining unit, the convertingfunction specifying unit does not specify the data converting functionand the converting unit does not convert the data to be converted. 3.The data converting apparatus according to claim 1, further comprising atable specifying unit that, based on the conversion rule code for theconversion source, specifies a corresponding conversion rule table fromthe data type conversion rule table or the cleansing rule table byreferring to the conversion rule, if mismatch is determined by thedetermining unit, wherein the converting function specifying unit, byreferring to the conversion rule table specified by the table specifyingunit, specifies the data converting function, according to thecombination of the metadata code for the conversion source and themetadata code for the conversion destination.
 4. The data convertingapparatus according to claim 1, wherein in the conversion rule table, ifthe metadata for the conversion source has an arbitrary value, a commondata converting function is assigned regardless of the combination ofthe metadata code for the conversion source and the metadata code forthe conversion destination, in the encoded meta-definition information,the metadata is directly used as a metadata code that specifies theconversion destination and the metadata for the conversion source havingan arbitrary value, the converting function specifying unit, byreferring to the conversion rule table specified by the table specifyingunit, specifies the common data converting function regardless of thecombination of the metadata code for the conversion source and themetadata code for the conversion destination, and the converting unit,by using the common data converting function specified by the convertingfunction specifying unit, converts the data to be converted.
 5. The dataconverting apparatus according to claim 1, wherein in the conversionrule table, if the metadata code for the conversion source and themetadata code for the conversion destination making up the combinationare different from each other, a given data converting function isassigned that converts data having the property prescribed by themetadata for the conversion source into data having the propertyprescribed by the metadata for the conversion destination, theconverting function specifying unit, by referring to the conversion ruletable specified by the table specifying unit, specifies the given dataconverting function, if the metadata code for the conversion source andthe metadata code for the conversion destination making up thecombination are different from each other, and the converting unit, byusing the given data converting function specified by the convertingfunction specifying unit, converts the data to be converted.
 6. The dataconverting apparatus according to claim 1, wherein in the conversionrule table, if the combination includes metadata for the conversionsource and metadata for the conversion destination, where the metadatafor the conversion source is specified in advance and the metadata forthe conversion destination differs from the metadata for the conversionsource, a given data converting function is assigned that converts theconversion source data to have the property prescribed by the metadatafor the conversion destination, the converting function specifying unit,by referring to the conversion rule table specified by the tablespecifying unit, specifies the given data converting function, if themetadata code for the conversion source and the metadata code for theconversion destination differ, and the converting unit converts the datato be converted by using the given data converting function specified bythe converting function specifying unit.
 7. The data convertingapparatus according to claim 1, wherein in the conversion rule table, ifthe combination includes metadata for the conversion source and metadatafor the conversion destination, where the metadata for the conversiondestination is specified in advance and the metadata for the conversionsource differs from the metadata for the conversion destination, a givendata converting function is assigned that converts the conversion sourcedata to have the property prescribed by the metadata for the conversiondestination, the converting function specifying unit, by referring tothe conversion rule table specified by the table specifying unit,specifies the given data converting function, if the metadata code forthe conversion source and the metadata code for the conversiondestination differ, and the converting unit converts the data to beconverted by using the given data converting function specified by theconverting function specifying unit.
 8. The data converting apparatusaccording to claim 1, wherein in the encoded meta-definitioninformation, the conversion rule code is assigned as sequential numbersin order of priority of the metadata, and the detecting unit, byreferring to the encoded meta-definition information, executes adetecting process of detecting the metadata code for the conversionsource and the metadata code for the conversion destination having theconversion rule codes identical at the conversion source and at theconversion destination in descending order of priority.
 9. The dataconverting apparatus according to claim 8, wherein the metadata isdescribed by an element selected from among a data type of the data tobe converted, a type attribute of the data type, and a value of the typeattribute, and in the encoded meta-definition information, a prioritysequence of the data type and the type attribute are set with respect tothe conversion rule code.
 10. The data converting apparatus according toclaim 9, wherein the detecting unit executes the detecting process forthe data type first and then executes the detecting process, accordingto the priority of the conversion rule of the type attribute.
 11. Thedata converting apparatus according to claim 9, wherein the detectingunit executes the detecting process for the data type first and executesthe detecting process in reverse order of the priority of the conversionrule of the type attribute.
 12. The data converting apparatus accordingto claim 8, further comprising an updating unit that updates, in theencoded meta-definition information, the metadata code that is for theconversion source and has been converted by the converting unit, theconverted metadata code for the conversion source being updated to themetadata code for the conversion destination before the next executionof the detecting process by the detecting unit.
 13. The data convertingapparatus according to claim 3, wherein the storage unit stores aconstraint condition table having a constraint condition set to restrictthe converting process by the data converting function, according to thecombination of the metadata code for the conversion source and themetadata code for the conversion destination, in the conversion rule,the constraint condition table is further correlated with the conversionrule code correlated with the data converting function having aconverting process restricted by the constraint condition, the tablespecifying unit specifies the constraint condition table correlated withthe conversion rule table before specifying the conversion rule table byreferring to the conversion rule, based on the conversion rule code forthe conversions source, if mismatch is determined by the determiningunit, the detecting unit, by referring to the constraint condition tablespecified by the table specifying unit, detects the conversion rule codeand the metadata code for the conversion source defined as theconstraint condition, according to the combination of the metadata codefor the conversion source and the metadata code for the conversiondestination and by referring to the encoded meta-definition information,detects the metadata code for the conversion destination matching theconversion rule code for the conversion source defined as the constraintcondition, the determining unit determines whether the metadata code forthe conversion source defined as the constraint condition detected bythe detecting unit matches the metadata code for the conversiondestination, the converting function specifying unit, by referring tothe conversion rule based on the determination result determined by thedetermining unit, specifies the data converting function, according tothe combination of the metadata code for the conversion source and themetadata code for the conversion destination, and the converting unitconverts the data to be converted by using the data converting functionspecified by the converting function specifying unit.
 14. A dataconverting apparatus comprising: a specification-definition informationacquiring unit that acquires specification definition information thatdefines a specification related to metadata for a conversion source andfor a conversion destination and defines a data converting function thatconverts conversion source data, which has a property prescribed by themetadata for the conversion source, to have a property prescribed by themetadata for the conversion destination; a first setting unit that setsa metadata encoding table that correlates with the metadata, a metadatacode specifying the metadata in the specification definition informationacquired by the specification-definition information acquiring unit; asecond setting unit that sets the conversion rule table by correlatingthe data converting function, according to a combination of the metadatacode for the conversion source and the metadata code for the conversiondestination; and a constructing unit that constructs a conversion ruleby correlating a unique conversion rule code with each conversion ruletable set by the second setting unit.
 15. The data converting apparatusaccording to claim 14, wherein if the metadata is special metadatacapable of having an arbitrary value, the first setting unit sets aspecial metadata encoding table that directly uses the metadata as themetadata code, and the second setting unit sets, for the specialmetadata, a conversion rule table correlated with the data conversionfunction that converts the special metadata for the conversion sourceinto the special metadata for the conversion destination.
 16. The dataconverting apparatus according to claim 14, wherein the first settingunit sets a metadata encoding table configured such that the secondmetadata in the specification definition information includes, as is,metadata in a lower hierarchy defined in the first metadata, if a secondmetadata in the same hierarchy as a first metadata defined in thespecification definition information has description defined to inheritthe first metadata.
 17. The data converting apparatus according to claim16, wherein the first setting unit does not set the metadata encodingtable for the first metadata.
 18. The data converting apparatusaccording to claim 14, further comprising a third setting unit thatcopies a conversion rule table having the data converting function setand assigns a constraint condition instead of the data convertingfunction to set a constraint condition table, if the constraintcondition is set for the data converting function, wherein theconstructing unit constructs the conversion rule by correlating, with aconversion rule code correlated with a data conversion function having aconverting process restricted by the constraint condition, theconstraint condition table set by the third setting unit.
 19. The dataconverting apparatus according to claim 14, further comprising: ameta-definition information acquiring unit that acquires meta-definitioninformation that defines metadata for the conversion source and for theconversion destination; and a generating unit that, for each of themetadata in the meta-definition information acquired by themeta-definition information acquiring unit, generates encodedmeta-definition information by assigning and encoding a conversion rulecode specific to the conversion rule table related to the metadata. 20.The data converting apparatus according to claim 19, further comprisinga compensating unit that compensates skipped metadata specified asdefault in the meta-definition information, if metadata in a lowerhierarchy of given metadata defined in the specification definitioninformation is specified as default, wherein the generating unitgenerates, for each metadata in the meta-definition informationcompensated by the compensating unit, encoded meta-definitioninformation by assigning and encoding a conversion rule code specific tothe conversion rule table related to the metadata.
 21. The dataconverting apparatus according to claim 19, further comprising: an inputunit that receives input of data to be converted; a detecting unit that,by referring to the encoded meta-definition information generated by thegenerating unit, detects the metadata code for the conversion source andthe metadata code for the conversion destination for which theconversion rule codes match; a determining unit that determines whetherthe metadata code detected for the conversion source and the metadatacode detected for the conversion destination by the detecting unitmatch; a converting function specifying unit that, based on thedetermination result obtained by the determining unit and by referringto a conversion rule constructed by the constructing unit, specifies thedata converting function, according to a combination of the metadatacode for the conversion source and the metadata code for the conversiondestination; and a converting unit that converts the data to beconverted by using the data converting function specified by theconverting function specifying unit.
 22. A data converting methodexecuted by a computer having access to a storage unit that storesencoded meta-definition information that assigns a unique conversionrule code to a metadata code that specifies metadata for a conversionsource and for a conversion destination and is in meta-definitioninformation defining the metadata for the conversion source and for theconversion destination, a data converting function that convertsconversion source data, which has a property prescribed by the metadatafor the conversion source, to have a property prescribed by the metadatafor the conversion destination, a conversion rule table that assigns thedata converting function, according to a combination of a metadata codefor the conversion source and a metadata code for the conversiondestination, and a conversion rule that correlates with each of theconversion rule tables, a relevant metadata code as a conversion rulecode, the method comprising: receiving input of data to be converted;detecting the metadata codes of the conversion source and the conversiondestination for which the conversion rule code matches between theconversion source and the conversion destination, by referring to theencoded meta-definition information stored in the storage unit;determining whether the detected metadata codes for the conversionsource and the conversion destination match; specifying the dataconverting function, according to the combination of the metadata codefor the conversion source and the metadata code for the conversiondestination, by referring to a conversion rule stored in the storageunit and based on the determination result obtained at the determining;and converting the conversion source data, which is the data to beconverted, to have a property prescribed by metadata for the conversiondestination, by using the data converting function specified at thespecifying.
 23. A data converting method executed by a computer andcomprising: acquiring specification definition information that definesmetadata for a conversion source and defines a data converting functionthat converts conversion source data, which has a property prescribed bythe metadata for the conversion source, to have a property prescribed bythe metadata for the conversion destination; setting a metadata encodingtable that correlates with the metadata for the conversion source, ametadata code specifying the metadata that is for the conversion sourceand is in the specification definition information acquired at theacquiring; setting the conversion rule table by correlating the dataconverting function, according to a combination of the metadata code forthe conversion source and the metadata code for the conversiondestination; and constructing a conversion rule by correlating a uniqueconversion rule code with each conversion rule table set at the settingof the conversion rule table.
 24. A non-transitory, computer-readablerecording medium storing therein a data converting program causing acomputer to execute a process comprising: storing encodedmeta-definition information that assigns a unique conversion rule codeto a metadata code that specifies metadata for a conversion source andfor a conversion destination and is in meta-definition informationdefining the metadata for the conversion source and for the conversiondestination, a data converting function that converts conversion-sourcedata, which has a property prescribed by the metadata for the conversionsource, to have a property prescribed by the metadata for the conversiondestination, a conversion rule table that assigns the data convertingfunction, according to a combination of a metadata code for theconversion source and a metadata code for the conversion destination,and a conversion rule that correlates with each of the conversion ruletables, a relevant metadata code as a conversion rule code; receivinginput of data to be converted; detecting the metadata codes of theconversion source and the conversion destination for which theconversion rule code matches between the conversion source and theconversion destination, by referring to the encoded meta-definitioninformation stored in the storage unit; determining whether the detectedmetadata codes for the conversion source and for the conversiondestination match; specifying the data converting function, according tothe combination of the metadata code for the conversion source and themetadata code for the conversion destination, by referring to aconversion rule stored in the storage unit and based on thedetermination result obtained at the determining; and converting theconversion source data, which is the data to be converted, to have aproperty prescribed by metadata for the conversion destination, by usingthe data converting function specified at the specifying.
 25. Anon-transitory, computer-readable recording medium storing therein adata converting program causing computer to execute a processcomprising: acquiring specification definition information that definesspecification related to metadata for a conversion source and for aconversion destination, and defines a data converting function thatconverts conversion-source data, which has a property prescribed by themetadata for the conversion source, to have a property prescribed by themetadata for the conversion destination; setting a metadata encodingtable that correlates with the metadata for the conversion source, ametadata code specifying the metadata that is for the conversion sourceand is in the specification definition information acquired at theacquiring; setting the conversion rule table by correlating the dataconverting function, according to a combination of the metadata code forthe conversion source and the metadata code for the conversiondestination; and constructing a conversion rule by correlating a uniqueconversion rule code with each conversion rule table set at the settingof the conversion rule table.